SourceLessXPlorer SourceLess Asgard
XPlorer following the chain as its own read-only node

height 176 of 178 on the network. 7 peer(s) connected, 45 known; 0 block(s) followed and 0 pulled in by sync since this follower started. This follower is BEHIND AND STUCK: peers are ahead of it and every one of them has been searched for a fork point without finding one. What is below is not the whole chain and will not become it without help. 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

Observed interval, median24 s
over 99 gap(s) between adjacent blocks. Mean 5 min, which one long gap moves a long way — the distribution below is the honest shape
Nominal slot3 s
the cadence this chain is configured for. A target, not a measurement — it is here to be compared against the figure beside it
Settled transactions per second0.017
over the window named below, not a peak and not a capability. 510 transaction(s) across the newest 100 of 176 block(s) this node holds, 77 to 176

Every figure on this page is counted over the newest 100 of 176 block(s) this node holds, 77 to 176. 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.

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.

at or under 1 slot (to 3 s)1
1 to 2 slots (to 6 s)4
2 to 10 slots (to 30 s)49
10 to 100 slots (to 5 min)29
over 100 slots (over 5 min)16
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
24 s 23,689 ms exactly
Mean
5 min 297,863 ms exactly spread (standard deviation) 23 min. Where the spread is of the same order as the mean or larger, the mean is not describing a cadence
Fastest
920 ms 920 ms exactly
Slowest
4 h 13,333,715 ms exactly the gap that ended at height 123, so it can be looked at rather than taken on trust
At or under the nominal slot
1 of 99 1% of the gaps, against a 3 s target

What the blocks carried

Transactions in the window510
Per block, mean5.1fewest 0, most 19 at height 99
Blocks carrying nothing0 of 100a measured zero, and the most useful number here: this chain seals no empty block, so every gap above is a period in which no transaction arrived

Every one of the 100 block(s) in this window carried at least one record: this chain sealed no empty block over it. So a gap between blocks is consistent with no record having arrived during it. 4 of them carried no transaction, but each carried STR.domain claims, which are records in their own right — so none of those is an empty block either. 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 ceiling400,000bytes. What this chain refuses to seal or accept past. Compiled in, not governed
Sealed bytes, mean3,848over 20 block(s), 157 to 176 — a tighter window than the one above, because weighing a block costs a canonicalisation and a public page must stay cheap to refresh
Signatures, share of held bytes75.2%THIS NODE’S OWN copy. A block is sealed with no signatures on it and collects them afterwards, so this is not a property of the chain — and on this chain it swings between almost all and none from one height to the next
BlockAgainst the ceilingSealed bytesTxsSignatures heldHeld, of ceiling
newest height 1761,721 0.4% of the ceiling0278 1 signature(s)0.5%
heaviest height 1757,220 1.8% of the ceiling114,276 15 signature(s)2.9%
lightest height 1761,721 0.4% of the ceiling0278 1 signature(s)0.5%

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 setBlocksWhat that means
closed12past the collection window, holding what this node collected. A final reading of what this node has — not necessarily of what every node has
collecting8inside 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

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.