DLE explorer

This page is the production reference for the public DLE explorer UI. It is not a production reference for DLE consensus, Archive Certificate, or tip execution. CoNET L1 routing wallets are documented on Global Archive Routing Registry.

The explorer is a read-only inspection surface for the isolated 30-day DLE Archive lab. It does not produce blocks, does not execute eth_call, and does not mint or burn assets.

Network facts

This hostname is an authorized CoNET path. Do not invent additional dle.* hostnames, and do not write explorer hostnames into Solidity constants. Production routing truth is the deployed L1 Global Archive Routing Registry, not this URL.

What the explorer is

The explorer answers one question: what is the isolated Archive lab reporting right now?

It shows:

• whether the proxied Archive process is healthy
• whether that process produces blocks or has a tip VM (both are false)
• CoNET-DLE Testnet eth_chainId (0x44c45) and the bootstrap Group ID (L1 register tx) as a hash capsule
• Clusters ((G_e)): live archive groups. Lab M6 fission shows 2. The second Group ID is the G2 L1 registerLiveGroup transaction 0xf781f2c2…876d5153
• heartbeat / health events
• fixture Archive rows used by the UI
• each Archive’s participant wallet (local seed, then a trusted L1 archivesOf overlay)
• first-group laboratory networked Archive Certificate status (not a production AC)

It does not show:

• a launched DLE tip chain
• production Archive Certificate / L1 wrapper / 30-day qualification
• Treasury lock / mint / burn
• Guardian listing as an honesty proof
• raw lab host inventories as a public API

The Archives page does display CoNET L1 224422 participant wallets for the bootstrap group. That is routing identity, not tip state and not 30-day qualification.

Pages

These public HTML routes returned 200 on 2026-08-14:

The explorer SPA source also defines /events/:eventId, /archives/:domainId, and a JSON-RPC probe page at /rpc. On the public host, POST /rpc is the Archive JSON-RPC facade. Do not treat a browser GET /rpc as a documented HTML page.

Same-origin API

The UI talks only to its own origin. nginx proxies those paths to the lab Archive listener. Clients should use the hostname, not unpublished lab IPs.

GET /health

Observed shape on 2026-08-14:

{
  "ok": true,
  "command": "archive",
  "runtime": "nodejs",
  "producesBlocks": false,
  "hasTipVm": false,
  "chainId": 281669,
  "chainIdHex": "0x44c45",
  "chainName": "CoNET-DLE Testnet",
  "port": 27101,
  "agent": "dle-30d-lab",
  "isolatedFromElCl": true,
  "lastQuorumOk": true,
  "lastPeerOk": 6,
  "liveGroupCount": 2,
  "liveGroupIds": [
    "0x3076a806de71ab75b2d48063cc3f1e7d8f8e3d54cb1d45a7469c75c9276f2ad0",
    "0xf781f2c23fe3b3dac09dc3e1929016b0af200ee93978e916df64d750876d5153"
  ]
}

Read this as lab process health, not BFT quorum and not Archive Certificate.

GET /api/v2/dle

Schema DleExplorerApiV1. The Home page uses liveGroupCount / liveGroupIds for the Clusters card (not tip height), plus certificate availability and the allowed JSON-RPC method list. Tip hash may still appear as a capsule.

Observed 2026-08-16:

• liveGroupCount: 2 (lab M6 fission; not 30-day qualification)
• liveGroupIds: [first-group L1 register tx hash, G2 L1 register tx hash]. Hosts emit those two txs. Explorer canonicalGroupId still aliases leftover laboratory keccak 0x7b3b8eb9…7f9b1a07 to 0xf781f2c2…876d5153 and Home does link that capsule to Blockscout /tx/.
• Legacy lab nodes may still emit dle.lab.group.v1; Explorer canonicalizes that alias to the first-group hash so it does not count as a third cluster
• tip.height after AC is typically "0x1" and is not shown as a Home metric
• certificate.available: first-group lab networked AC may be true; still not 30-day qualification

Related reads:

POST /rpc

This is a read-only DLE facade, not an Ethereum execution RPC.

The explorer Home page states the same rule: DLE has no tip VM, so eth_call, eth_estimateGas, and eth_sendRawTransaction are rejected.

Three identifiers that must not be mixed

Do not configure a wallet, bridge, or dapp to 0x44c45 as if it were CoNET L1 or a launched DLE tip chain.

Lab status the explorer does not upgrade

The public UI being live does not close these whitepaper / spec gates:

What not to do

• Do not treat https://dle.conet.network/ as Blockscout or as mainnet.conet.network.
• Do not send asset, swap, or UserOp traffic to POST /rpc.
• Do not publish lab host IPs, billingRef values, or SSH targets from explorer fixtures.
• Do not write dle.conet.network into contract constants.
• Do not treat 0x44c45 as CoNET L1 or as Group ID. Do not display L1 uint 1 as Group ID.

See also

• Layer 2 overview
• Global Archive Routing Registry
• Archive plane
• Design thesis
• CoNET L1 RPC and explorer
• Lab honesty track
• Developer quick start: Layer 2