height 23715 of 23715 on the network. 9 peer(s) connected, 77 in its peer directory; 1011 block(s) followed and 840 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.
Network status
Measured as this page was served, at 2026-11-06 18:43:39.611Z by this node’s clock. The three figures above update while the page is open; reload for the rest.
This is one node’s reading, not the network’s
There is no such thing as a measurement of the whole network taken from inside it. Every figure on this page is what the node serving it has verified for itself, and the banner at the top of this page says which chain that is and how it was obtained. A node that is still syncing holds a chain that is internally perfect and is not yet the whole one; where it can tell, it says how far behind it is, and where no peer has advertised a height it says that rather than drawing itself as caught up.
So read the height as this node has verified this many blocks. A second opinion is another node, and the honest way to get one is to run one.
The head, in detail
- Head finality
- confirming
- Transactions in the head
- 0
- Last observed gap
- 1 min one sample. The distribution over a named window is the figure worth having
- Mempool
- 0 of 8,192 held. The queue itself
These are the only figures this surface updates on a timer, and they are the only ones cheap enough to. The seat count, the quorum and the participation window on the page are chain state read at a height and a fold over a hundred blocks; refreshing those every few seconds for every open tab would make a public page the most expensive thing a node does, so they are deliberately not polled. They are as of the moment the page was rendered, and a reload is what moves them.
The status of this surface
- What it is
- A read-only window. It holds a narrowed view of the chain that carries no method able to change it, answers GET and HEAD only, and never reads a request body.
- Cheapest route
/head, which is what this page’s live figures poll and the route to use if you are watching a chain from a script rather than from a browser.- Liveness
/health, deliberately thin: a health check must not be a way to make a node do work.- Everything it serves
/apipublishes the whole route table, and the API page renders it with the node’s method catalogue beside it.
Not published yet
- Not published yet: a list of the hosts that are expected to be up. The figures above are this one node’s, and say nothing about any other host.
- Not published yet: an uptime figure. This page measures how old this node’s head is and how far its finality line trails it, as of the moment it is served; neither is uptime over a window, and no uptime is claimed.
- Not published yet: an incident history, or a place incidents will be published.
- Not published yet: a maintenance calendar.
- Not published yet: a contact for an outage, or a time within which one will be answered.
- No availability commitment is published, so this page offers none.
The same list is at /api/status.