Skip to main content
Testnet

Celestia Mocha network

Celestia's public testnet, where validators rehearse upgrades and new features before mainnet. Validators, uptime, governance and jailing.

Typical fee 0.0003 TIA

Network

Updated
Next day in
Cosmos chains have no epochs, so BitBasic uses the UTC day, midnight to midnight, as the dashboard's period and names it by its date.
10h 55m Day Nov 6 Hour 14 / 24
Health
Whether the chain made its latest blocks at its normal pace. BitBasic takes about 30 minutes' worth of the latest blocks and compares the time they took with the normal block time: the average over the last 100,000 blocks (or fewer where nodes keep less history), measured hourly. 100 means the usual pace. It drops to 0 when no new block has arrived for 20 normal block times, and never sooner than a minute. Healthy at 90% or more, Degraded from 70% to under 90%, Unhealthy below 70%.
Healthy
99.8% · 628 blocks in the last 30m 02s; 629 expected at the normal 2.864 s a block
Active validators
A node that stakes tokens, its own and its delegators', to sign and propose blocks. Only the validators with the most stake make the active set and earn rewards.
89
1 queued · 0 exiting
All validators
Total stake
Tokens locked up to back a validator. Total stake includes tokens delegated by others.
368.32M TIA
Block height
The number of the latest block: how many blocks the chain has made so far.
2,371,631
Bonded ratio
The share of all tokens in supply that is staked with validators. Staked (bonded) tokens earn rewards, can be slashed with their validator, and take 14 days and 1 hour to unstake.
17.3%
Of 2.12B TIA in supply
Average block time
2.86 s
Over the last 100,000 blocks
Signing window
How many recent blocks the chain checks to see if a validator is offline. A validator that signs too few of them (less than the minimum signed) is jailed for downtime.
10,000 blocks
About 8 hours; signing under 0.1% of it gets a validator jailed
Fibre servers
How many validators in the active set have a Fibre server registered on chain, and the share of the active stake they hold. A registration doesn't prove the server answers.
87 of 89
Active validators with a Fibre server registered on chain · 99.7% of stake

Block production per day

Blocks made vs. what the normal block time would give, last 1 day

Updated
Average rate
Blocks the chain made as a share of what its normal block time (the average over the last 100,000 blocks, or fewer where nodes keep less history) would give over the time BitBasic counted. Cosmos has no slots, so under 100% means the chain ran slower than usual, not that blocks were skipped.
—
completed days only
Blocks
—
completed days only
Blocks behind pace
How many fewer blocks the chain made than its normal pace would give. BitBasic divides the time it counted by the normal block time (the average over the last 100,000 blocks, or fewer where nodes keep less history) and subtracts the blocks made. Cosmos chains have no fixed slots, so this shows the chain slowing down, not validators failing. A day at the usual pace shows 0. Blocks a validator did not sign are on its own page, as Missed blocks.
—

Counting started Nov 6, 12:55 UTC. The figures above appear once the first full day, Nov 7, ends at 00:00 UTC on Nov 8.

99% or more 95%–99% below 95% in progress

All days as a table

Latest blocks

Updated
Block Producer Transactions Age
#2,371,631 Solva (CryptoCrew) 1
#2,371,630 Smart Stake 1
#2,371,629 NakoTurk 0
#2,371,628 ECAD Infra 1
#2,371,627 ITRocket 0
#2,371,626 mammoth.guru 1
#2,371,625 01node 1
#2,371,624 devops 2

Validators

Updated
Active
In the active set: signs and proposes blocks, and earns rewards.
89
Queued
Outside the active set: not enough stake to be among the validators that sign blocks, so it earns nothing. It joins by itself once its stake ranks high enough.
1
Jailed
Removed from the active set, so it earns nothing. Its delegators earn nothing either until its operator unjails it. Most jailings are for downtime: signing too few of the recent blocks. The operator can unjail it after a jail period of 1 minute. A validator is also jailed when its operator withdraws its own stake below the minimum it set. BitBasic shows a validator as jailed for 28 days and 2 hours after the jailing; after that it counts as exited.
2
Exited
Left the validator set, permanently or for a long time. Tombstoned validators (banned forever for double-signing) count as exited, and so do those jailed more than 28 days and 2 hours ago and never unjailed, and those fully unbonded and removed from the chain's list of validators.
2

Top by stake

  1. devops 43.9M TIA
  2. P-OPS Team 23.4M TIA
  3. Qubelabs 22.3M TIA
  4. NakoTurk 21.1M TIA
  5. ITRocket 10.1M TIA

BitNordic

Why is this here?

BitNordic doesn't run a validator on Celestia Mocha.

Networks BitNordic runs

All validators

Governance
How the chain decides upgrades and changes to its settings. Anyone can put up a proposal with a deposit; staked tokens then vote on it, and a validator's vote counts for its delegators unless they vote themselves.

Updated
Open proposals
0
None in voting now
Proposals
0
Quorum
The share of all staked tokens that must vote on a proposal, any option counting, for its result to stand. A proposal that misses it fails, whatever the votes say.
33.4%
Voting lasts 1 day (23h 59m if expedited)

Recent proposals

No proposal has gone to a vote yet.

All proposals

Jailing
A validator that signs too few blocks is jailed for downtime and loses none of its stake. One that signs two different blocks at the same height is tombstoned (banned forever) and loses 2%. Its delegators lose the same share. A validator whose operator withdraws its own stake below the minimum it set is jailed too, but loses nothing. BitBasic dates a jailing by when the validator left the active set, which the chain records for every kind of jailing.

Updated
Jailed recently
Jailed in the last 28 days and 2 hours and not unjailed since. These validators show as Jailed: they earn nothing until their operator unjails them. After 28 days and 2 hours BitBasic counts them as exited.
2
In the last 28 days; still jailed
Jailed long ago
Jailed more than 28 days and 2 hours ago and never unjailed. BitBasic counts these validators as exited. Their delegators earn nothing until they move their stake to another validator.
2
Over 28 days ago and never unjailed: counted as exited
Tombstoned
Banned forever for signing two different blocks at the same height. This is called double-signing. The validator loses 2% of its stake, and its delegators lose the same share. It can never sign blocks again, so BitBasic counts it as exited.
0
Banned forever for double-signing
Signing window
How many recent blocks the chain checks to see if a validator is offline. A validator that signs too few of them (less than the minimum signed) is jailed for downtime.
10,000 blocks
Minimum signed
The share of the signing window a validator must sign, or it is jailed. A validator below it is jailed for downtime: it loses none of its stake and earns nothing until its operator unjails it, at the earliest 1 minute later.
0.1%
Of the window; below it a validator is jailed for at least 1m 00s

Recently jailed

  • vessano jailed For downtime · free to unjail since Oct 26, 03:08 UTC 1w ago
  • Anam145 jailed For downtime · free to unjail since Oct 22, 15:15 UTC 2w ago

All jailed validators Lowest uptime first