Independent analytics by X PrimeFlow. Not affiliated with, endorsed by, or sponsored by the Celestia project, its foundation or its developers.
Celestia data availability, measured
Blob traffic counted from the chain by our own collector, the next network upgrade and how far validators have signalled it, data-availability parameters, staking and governance. Every section names its public source and the time of reading; X PrimeFlow does not run a Celestia read node of its own.
Reading Celestia from public endpoints…
Network
PUBLIC SOURCES Live- Block height
- —
- Block time
- —
- App version
- —
- Next upgrade
- —
- Blob data, 24 h
- —
Counted by our own collector from PayForBlobs transactions in windows of 100 blocks; a window is written only when all of its transactions are read.
Blob traffic
Top namespaces by blob data, 24 hours
Celestia moves to a new app version through validator signals (x/signal), not a governance vote: once signals reach the threshold of voting power, the upgrade is scheduled at a height.
Active set
When TIA leaves Celestia over IBC, the original stays locked in the escrow account of its channel on Celestia. A channel escrow balance is the TIA currently held on the chain at the other end.
TIA in IBC escrow by channel
Latest proposals
Every number on this page comes from these open endpoints.
What this page does not claim
- X PrimeFlow does not run a Celestia read node yet: every reading comes from a named public endpoint.
- Blob traffic is our own measurement since the collector started; earlier history is not shown.
- The upgrade time is an estimate; the chain upgrades at the scheduled height.
- Namespaces are shown by identifier; a rollup is named only when an open source confirms it.
- TIA in IBC escrow is the balance of each channel escrow account; an unread balance is shown as unknown, never as zero.