shreds

Vyra Labs testnet validator · Singapore · UDP 8001connecting
slot -leader -updated -
Last 120 slots
grouped by leader window of 4 slots, newest on the right
complete4+ data shreds rebuiltnever completedno shreds, skipped or ours
Packets in
-pkt/s
kernel drops -
Data shreds missing
-%
in complete slots, last minute
Set ready p50
-ms
p99 - ms
Transactions rebuilt
-%
held bytes that never arrived
Missing data shreds per slot
rebuilt from backup shreds, red where the slot never completed
Set ready time, last 10 min
first shred of a set to its 32nd, in ms
collecting · 0.0 of 10 min
Recent slots
SlotLeaderTxsMissingSlot timeFinalResult
Integrity, last minute
Bad Merkle proofs-Bad leader signatures-Slots closed-Slots never completed-Slots with no shreds-Messages dropped-Publish lag-
Sampled transactions

A set needs any 32 of its 64 shreds, so missing data shreds are rebuilt from backup shreds. A slot with no shreds was skipped by its leader, or was one of ours, which never reach us inbound. Stats cover the last minute and refresh every 5 seconds, slots appear as they close, about 1.5 seconds after their first shred. Warning levels are provisional until set from a day of real data.