BITCOIN NETWORK OBSERVATIONS
Network health
Explore endpoint consistency and estimated mining power over time. Each measurement keeps its source and observation date.
Experimental measurements. No overall health score is computed.
Observed components Experimental
These observations track whether the same endpoints keep answering from day to day, what they advertise, and how the estimated hashrate changes over time. Consistency needs several days of observations, so it is reported only for endpoints attempted on at least three days.
Loading health observations…
| Component | Observation | What it means |
|---|
Over the 30-day window
A single day's census catches each endpoint at one moment, so a node that misses one dial drops out of that day. Here an endpoint counts under each state it showed on at least half of the days it was attempted, over every version response, whether or not it advertises compact filters. That is why the split and ahead counts are larger than the daily census's, which count usable peers only.
| Network | Assessed | Answered | Near the tip | At the BIP-110 split | Over 100 blocks ahead |
|---|
Hashrate is estimated from the work in mined blocks and the time between them, so short windows are noisy. Pool attribution says which pool published a block, not who owns the hardware. No overall score is computed yet.
Health components and provenance · Per-endpoint observations (JSON.gz) · Definitions and reproducible calculation · Mining source methodology and API