Loading
Connecting…
Network health
No data yet
Estimated hashrate
—
from the current difficulty
Average block time
—
target 30 s
Block reward
—
slow start
Connections on the seeds
—
nodes and wallets connected now
Known node addresses
—
in the seeds' address books
Pending certificates
—
waiting for a block
Block times
Seconds each recent block took to arrive
- 30 s target
- reorg
Latest blocks
| Height | Age | Took | Certs | Id |
|---|---|---|---|---|
| No blocks yet. | ||||
Estimated network hashrate
Difficulty divided by the 30-second target; it lags real changes by a few dozen blocks
Reward slow start
The block reward rises in a straight line over the first 86,400 blocks, about 30 days
Seed nodes
The nodes a new install dials first. Capacity is how many of a seed's inbound slots are taken.
| Seed | State | Height | Tip | Peers | Inbound capacity | Nodes / wallets |
|---|---|---|---|---|---|---|
| No data yet. | ||||||
How to read this page
- Where the numbers come from. A collector reads the public RPC of the project's seed nodes every few seconds and publishes one file; this page reads that file. It never talks to a node directly, and it lists no peer addresses.
- Hashrate is an estimate. It is the current difficulty divided by the 30-second block target, so it trails a sudden change by a few dozen blocks.
- Connections are not a node count. A node connected to two seeds is counted on both, and a node connected to none is not counted. The seeds see their own connections, not the whole network.
- A short reorg is normal. Two miners finding a block seconds apart is expected at a 30-second target; one of the two blocks is replaced. Deep reorgs are what the health check watches for.
- All times are UTC.