XPlorer following the chain as its own read-only node

height 23698 of 23698 on the network. 9 peer(s) connected, 77 in its peer directory; 994 block(s) followed and 824 pulled in by sync since this follower started. Caught up: this follower holds every block any peer has claimed, so every panel below is the whole chain. Genesis 1cf8655125cc1bbb…, producers genesis.

What this follower is, locally

Following 7 seed(s) — their addresses are not published here, for the reason the peer table gives. Its store is held under its own Cerberus lease — no other node’s store is opened, touched or stopped.

Explorer as a Service

The software is in this build. A hosted service is not.

Nothing in this repository runs an explorer on anybody else’s behalf, and there is no price, no uptime commitment and no onboarding. What exists, and is described below, is an explorer you can point at a chain yourself in minutes.

XPlorer is not a service sitting beside the chain with its own index. It ships inside the node binary, reads the chain through a view that carries no method able to change it, and serves its own stylesheet, script, brand marks and typefaces — so there is no CDN, no database and no second deployment to maintain.

Four ways to point it at a chain

Follow the network: Give it a peer address and it syncs the chain into a directory of its own as a read-only node, then serves every panel over a live network — with no key, no operator credential, and nothing stopped or touched on anybody else’s node. This is the mode a public explorer should run in.
A stopped node’s directory: Opened under a lease because nothing else holds it, replayed in this process. Every panel, served from the blocks that node actually sealed.
A running node, over its operator endpoint: No directory is opened — a second store on a live data directory is what corrupts the log being read. The endpoint publishes a head and peers and no block bodies, so this view is genuinely partial, and every panel it cannot serve answers with the reason rather than with a 404 that says the panel does not exist.
A synthetic chain: Built in memory for a demonstration, and labelled as synthetic in a warning banner on every page, because a made-up chain taken for a real one is the worst thing this surface could do.

Whichever it is, the banner at the top of every page says so. The provenance is part of the page rather than a deployment note somebody has to be told.

What you get without writing anything

Every panel this surface has: blocks, transactions, addresses, contracts with a read panel, identity, organisations, delegations, supply, governance, the bridge, hostless spaces, messaging records, the producer roll, consensus, throughput and cryptography.
A JSON mirror of every one of them, bounded and clamped, with amounts as decimal strings and unmeasured values carrying a reason.
Both themes, a keyboard path through every control, and a content security policy that refuses third-party anything.
Mounting it inside a server you already run is a constructor and one call. A node that already listens does not need a second port.

What a hosted service would have to add

Named so that the gap is specific rather than a shrug: a machine and a network to run it on; a name and a certificate; somebody watching whether it is up; a path for the chain to be re-synced when it is not; and a person to answer when a reader says a panel is wrong. Every one of those is an operational commitment, and none of them is in this repository.

Not answered here

Each of these is a decision rather than a measurement, so nothing in this build could supply one. They are listed here, and again at the JSON mirror of this page, rather than filled with something that would read as true.

[WHETHER A HOSTED SERVICE IS OFFERED AT ALL — to be supplied]
[PRICING, AND THE TIERS IT IS SOLD IN — to be supplied]
[AVAILABILITY COMMITMENT AND WHAT HAPPENS WHEN IT IS MISSED — to be supplied]
[WHICH CHAINS WOULD BE SUPPORTED, AND ON WHOSE AUTHORITY — to be supplied]
[WHETHER THE SURFACE MAY BE REBRANDED, AND UNDER WHAT LICENCE — to be supplied]
[ONBOARDING AND THE COMMERCIAL CONTACT — to be supplied]
[DATA RESIDENCY AND WHERE A FOLLOWER’S CHAIN COPY WOULD LIVE — to be supplied]
[SUPPORT HOURS AND ESCALATION — to be supplied]