Paid, 10 min
0
shards, for blocks of any age
The devnet explorer · proving
Proving on the devnet.
Every chain block's execution is split into shards. Miners prove them, the node verifies the proofs, and a later coinbase pays the prover. This page reads the observer's record of that cycle: the plan per block, who proved what, and how long a block waits to be paid.
Proving
OFFLINE
the node's proving layer
Paid, 24 h
0
shards, IGN to provers
Open blocks
0
chain blocks with unpaid shards
Provers, 24 h
0
vote keys paid for a shard
Latency, 1 h
n/a
median DAA from block to payment
Pool
0
records in the node's pool
Shard budget
0pgas
proving gas per shard
Chain blocks
newest 60, every 5 s
| Number | Block | DAA | Class | Miner | Txs | pgas | Shards paid | States | Median lag, DAA | Time |
|---|---|---|---|---|---|---|---|---|---|---|
| Loading. | ||||||||||
States count the block's shards as planned (the node published the plan), proving (a record is in the pool), verified (the node's verifier accepted the proof) and paid (a later coinbase carried the record). Lag is the DAA score of the paying block minus the block's own; the devnet targets one DAA step per second.
Provers, 24 h
by shards paid
| Prover | Shards | Paid, IGN | Median lag | Last hour | Last paid |
|---|
A prover is a vote key (its first 8 hex characters). A card runs several keys, so one machine can be several rows.
Block to paid
the last hour
Measured on the shards paid in the window, from the proven block's DAA score to the paying block's. The 24-hour totals by state are below the hour.
Four words, used exactly. Included: the block carries the transaction. Executed: the EVM ran it and the result is on the record. Proven: a valid proof record for its block was carried and paid. Finalised: the block sits under a certified checkpoint, two thirds of active and of total weight. A pause in finality is shown as a pause, never as a block losing its lock. Recovery lock: after a full weight window with no lock, a checkpoint signed by more than half of the anchored weight; shown as a recovery lock, never as finalised. On the devnet’s current node line the lock kind is reported by the forming node only: a node that received the certificate records an ordinary lock, so a recovery lock can read as final on a receiving node until the 2.0.3 node line lands. The definitions are the finality specification’s: section 9, the guarantees.