height 25517 of 25517 on the network. 9 peer(s) connected, 94 in its peer directory; 2813 block(s) followed and 2293 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.
Speed, as measured
Every figure on this page is counted over the newest 100 of 4,096 block(s) this node holds in memory, 25418 to 25517. There is no peak, no best case and no projected figure anywhere on it, and no field in the data behind it that one would fit in.
- gap between adjacent blocks, oldest left
- nominal 3 s slot
- median 1 min
Top of the plot is 13 min, the slowest gap in this window, at height 25436; the fastest was 1 min. The axis is linear from zero to that slowest gap, so a single spike over a floor is the measurement and not a drawing fault. 99 gap(s), heights 25419 to 25517. The distribution and every exclusion behind it.
Observed interval, against the nominal slot
The gap between one block and the next, differenced from the blocks’ own timestamps. Those timestamps are each the producing seat’s clock rather than a shared one, so a gap is as accurate as the two clocks either side of it.
- Gaps differenced
- 99 adjacent heights only. A hole in what this node retains is not a slow block, so a pair either side of one is never differenced
- Median
- 1 min 63,857 ms exactly
- Mean
- 2 min 96,448 ms exactly spread (standard deviation) 2 min. Where the spread is of the same order as the mean or larger, the mean is not describing a cadence
- Fastest
- 1 min 60,053 ms exactly
- Slowest
- 13 min 804,859 ms exactly the gap that ended at height 25436, so it can be looked at rather than taken on trust
- At or under the nominal slot
- 0 of 99 0% of the gaps, against a 3 s slot. A gap at or under one slot is a seat sealing in the very next slot; a longer one is slots that passed with no block, because their seat was absent or had nothing to seal
What the blocks carried
100 of the 100 block(s) in this window carried no record of any kind, so this chain does seal empty blocks and a gap is NOT evidence that nothing arrived. What a gap is not, either way, is a verdict: the absence of a block is equally consistent with no producer having been running, and nothing in a chain distinguishes the two — an operator’s own surface can see whether seats were up and a public explorer reading a chain cannot. A page that resolved this to “idle and healthy” would be guessing for the reader in the one case where guessing is worst.
What a block weighs, and what takes the room
| Block | Against the ceiling | Sealed bytes | Txs | Signatures held | Held, of ceiling |
|---|---|---|---|---|---|
| newest height 25517 | 1,248 0.3% of the ceiling | 0 | 33,997 119 signature(s) | 8.8% | |
| heaviest height 25517 | 1,248 0.3% of the ceiling | 0 | 33,997 119 signature(s) | 8.8% | |
| lightest height 25498 | 1,248 0.3% of the ceiling | 0 | 32,013 112 signature(s) | 8.3% |
- header and records
- transactions
- signatures held by this node
- unused
Bytes are counted with the chain’s own canonical encoding — the same measure `produceBlock` weighs a block against this ceiling with, so these figures and that refusal are in the same units. Sealed bytes are the header, the transactions and the records; a block is sealed with no signatures on it and collects them afterwards, so the signature bytes are what THIS node has accumulated and are labelled apart.
| Signature set | Blocks | What that means |
|---|---|---|
| closed | 12 | past the collection window, holding what this node collected. A final reading of what this node has — not necessarily of what every node has |
| collecting | 8 | inside the collection window: this node may still receive more signatures for these, so their held size is a live reading rather than a final one |
2 retention states, and this is all of them — not a page of a longer list.
A block grows after it is sealed. produceBlock weighs it against the ceiling with no signatures on it, and acceptBlock weighs what arrives — signatures included — so the two right-hand columns above are the distance between a block that was legal when it was sealed and the same block as a catching-up peer would receive it.