Attestations
Current epoch - 13949
2026.10.27 at 04:20:19 (29m 37s left)
Live attestation queue
Attestation archive
Validator attestation history
The same archive sliced per epoch: pick any past Starknet epoch to see exactly which validators attested in it, at which block, and which ones missed.
Attestation data is read live from the Starknet staking and attestation contracts. A missed attestation forfeits the entire epoch’s rewards for the validator and its delegators, so the archive above is a direct uptime record.
Starknet attestations — FAQ
What is a Starknet validator attestation?
Every epoch each Starknet validator is assigned one block it must attest to inside a fixed attestation window. The assignment is derived from the validator’s stake and the epoch id, and the attestation proves the validator is online and following the chain.
What happens if a validator misses an attestation?
Rewards on Starknet are all-or-nothing per epoch: a validator that misses its attestation earns nothing for that entire epoch — and neither do its delegators. That makes attestation history the most direct uptime and reliability signal when choosing a validator.
How often do attestations happen?
Once per epoch per validator. On mainnet an epoch is about an hour, so a healthy validator produces roughly 24 attestations a day. The live queue on this page shows which validators have already attested in the current epoch and which are still pending.
What does the attestation map show?
Each dot is one validator in the current epoch: filled dots have already attested, outlined dots are still pending. Pending validators are shown first, and newly completed attestations pulse into the map in real time.
Where does this data come from?
Upstark reads attestation events and epoch data directly from the Starknet staking and attestation contracts over RPC — no third-party explorers. The historical archive tracks attested and missed epochs per validator since indexing began.