XPlorer following the chain as its own read-only node

height 23701 of 23701 on the network. 9 peer(s) connected, 77 in its peer directory; 997 block(s) followed and 827 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.

Knowledge base

The questions this chain actually gets asked, each answered by a page that measures itself rather than by an article somebody has to remember to update. Where the answer is long enough to be a document, the document is named.

Start here

What is a block explorer — and what this one cannot tell you
Is the chain moving — height, the finality line, and how long ago the head sealed
Did my transaction settle — sealed transactions, with the mempool beside them
What is behind a name — STR.domains, and the wNFT that proves each one
What has the chain just done — blocks newest first, and what each one carried

If you already have an identifier — a height, a block hash, a transaction id, an address, a domain or a contract — paste it whole into the band at the top of this page. Paste it whole: a shortened hash does not resolve, and where nothing matches, this surface says so rather than guessing.

How to read this surface

Unknown is not zero: A figure this node could not measure says unknown and gives the reason. It is never filled with a zero to make a panel look complete, and the three things a zero could otherwise mean — a measured nothing, a fact that there is no limit, and a thing nobody looked at — are kept apart everywhere.
The banner at the top of every page: Says which chain is underneath it, and there are four answers: a stopped node’s own directory, a running node read over its operator endpoint, this process following the network as a read-only node of its own, or a synthetic chain built in memory. The last one is a warning, because a made-up chain being taken for a real one is the failure that banner exists to prevent.
Sealed is not final: A block at the head has been sealed. A block at or below the finality line will not be reorganised. Consensus shows the distance between the two and what closing it takes.
Pending is not paid: A transaction in the mempool is in no block. It has not settled and it may never. The mempool is labelled as the mempool everywhere it appears.
A list is a page: Every list here is bounded, states its own bound, and offers only the page sizes the server will honour. A count of 25 rows is not a claim that the chain holds 25 things.
One node is not the network: Every figure here is what the node serving this page has verified. A follower that is behind holds a chain that is internally perfect and is not the whole chain, and it says so rather than presenting a short chain as a complete one.
There are no fees: A transaction on this chain carries no fee to a producer. Where a panel would normally show one, it states that instead.

The published documents

A corpus of documentation is published beside the node installers, with a SHA-256 row for every file so a reader can check that what they downloaded is what the repository holds. The documents are published unchanged: where one says a thing is unmeasured, it says so on the download host too. They are grouped by who is reading:

Running a node — you have downloaded an installer, or are deciding whether to. Start with HOW_IT_WORKS.md, and read MAINNET.md before pointing anything at a live network. RUNNING_A_SEAT.md is the one that says what operating a validator seat obliges you to.
Building on the chain — JSON_RPC.md is the reference everything else sits on, and the method catalogue on this surface is generated from the same array that document is checked against.
What this chain is — LITEPAPER.md for the condensed reading and WHITEPAPER.md for the full one. Both carry a section on what is NOT proven.
The rules of the system — where the supply comes from, who can change what, what a name is, and the register of every component name.
In depth — volumes on each layer, in which every claim cites a source file and a line, and a checker re-reads those citations against the tree because line numbers move whenever anybody edits a file.

This page does not link to them. Nothing on this surface is fetched from another origin and nothing here links to an address this build cannot verify, so the published location is a gap below rather than a URL typed into a renderer.

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.

[THE PUBLISHED DOCUMENTATION URL, IF THIS SURFACE SHOULD LINK OUT TO IT — to be supplied]
[WHETHER THE CORPUS SHOULD BE SERVED BY THE NODE ITSELF INSTEAD — to be supplied]
[A SUPPORT OR QUESTION ROUTE FOR SOMETHING NO DOCUMENT ANSWERS — to be supplied]
[WHICH LANGUAGES THE DOCUMENTATION IS PUBLISHED IN — to be supplied]