Consensus

Seats on the roll

1313

Seats that have sealed

309 of 1313

Slot length

3 s nominal, a turn and not a block interval

Observed interval

observed median 1 min over 99 gaps between blocks 28374–28473 the distribution is on Throughput

Slot at the head

598144261

Whose turn

STR.GENESIS0562 zk13str_…5e0_3897copy

The turn is decided by the clock and not by the height, so a seat that is absent does not stop the roll: its slot passes and the next occupied seat seals. That is why a partly-filled roster produces a chain that advances slowly rather than one that stops.

The order consensus rotates over, read at the head’s height. It is not the same question as who MAY seal — a seat can be on the roll and absent from a rotation resolved at a different height — so the two are two pages.

← newer 951–975 of 1,313, at most 25 per page rows 2550100 older →

Every position in the rotation is reachable from this control. The validator roll answers the other question — who may seal at the head, what each has bonded, and every admission and eviction that got the roll here.

Drawn from the page of the rotation above, and from the block headers this node holds. A seat that has sealed nothing is not drawn: a column of zero height for most of a roll would be a picture of the rotation’s length rather than of its work.

Every block on this chain was sealed by a seat on the roll. On a production realm that is the claim worth making, and it is made by this list being empty rather than by a sentence saying so.

Height read at

28473

Seats on the roll

1,313

Quorum a block must reach

876 of 1,313 seated seats — two thirds plus one, read from the chain’s own seating rather than recomputed here

Head block

28473 under the threshold by this node’s count of the signatures it holds. This chain has never reached its threshold, so this is its normal state rather than an incident — and finality does not depend on it: the line is a fixed depth below the head and reads no signature at all

Distinct seats that signed it, as this node holds them

100 7.6% of the roll, counted from the signatures THIS node holds for the block. Not a chain fact: the set is outside the block hash and each node collects its own

Window

100 blocks, 28374 to 28473 the newest blocks only — this is a public route and a fold over a whole chain is work a refresh should not be able to buy

Seats signing, typically

101 mean over the window; fewest 84, most 134, about 7.7% of the roll

Blocks that reached the quorum

0 of 100 0% of the window

Distinct seats SEEN in the window

308 of 1,313 on the roll — 23.5% — each one identified by a signature inside a sealed block, over the 100 blocks of 100 in this window that this node holds a signature set for, 28374 to 28473. 10,121 signatures in total before de-duplication. This is not a count of seats online. A seat missing from it has very likely not had a turn, and which signatures reached THIS node is a local matter

Distinct seats that sealed

60 of 1,313 on the roll, counted from the block headers over the same window. Far smaller than the figure above, and that is arithmetic rather than a finding: the rotation gives each seat one slot, so a full turn of this roll takes about 1 h and a window of 100 blocks cannot contain most of it

Two different kinds of figure are above, and the difference matters more than any of the numbers. The seats on the roll and the quorum threshold are CHAIN STATE, read at a height: every honest node answers them identically. The signature counts are THIS NODE’S OWN EVIDENCE: a block’s signatures are carried outside its hash, are agreed by nothing, and are collected by each node for itself after the block is sealed, so two honest nodes legitimately hold different sets for the same height — seven seats asked for the same heights at one moment returned six different counts for one of them. A second explorer on this chain may therefore show different signature counts and neither is lying.

Finality does not depend on any of it. The line is a fixed depth below the head, ratcheted, and reads no signature at all — so a block carrying none is finalised exactly as one carrying the whole roll is, and a count beside a finality line must not be read as its cause.

What is deliberately absent is a count of how many seats are ONLINE. No single node can measure that — a seat that is up and silent looks exactly like a seat that is down — and a number for it would be invented.

Blocks inspected

28473

Blocks whose signatures this node no longer holds

1

Blocks carrying attestations

4095

Blocks holding exactly their cap

0

Attestations in total

464805

Quorum threshold

unknown

this explorer was not given a validator registry, so it has not looked. GenesisNodeRecord names producers by address and Valhalla admission needs a public key the genesis does not carry.

These four are counted over every block this node holds, which makes them lifetime totals. The section above is the same question asked about now, and it is the one that says whether this chain is agreeing today.

Attestations are signatures OVER the block hash and are carried outside the hashed content, because they cannot be inside the thing they sign.

1 block is counted in neither of the two rows above. This node dropped their signatures after they went final, or never collected any and can no longer be given one, so their zero is this node’s retention and not a statement about who signed. A ratio taken over every block inspected would be reporting that policy as a finding about the roll.

Head

28473

Finality line

28462

Confirmations required

12

Deferred depth

3

A header commits to the state root as of height minus the deferred depth, so the root in the newest header is not the root of the newest state.