Data Status

This page states, in plain terms, how fresh and trustworthy the data on Mining Scan is right now. The number below is the very same 0–100 our own watchdog uses to page us — there is no separate, prettier score for visitors.

49/ 100   Honesty IndexImpaired
SignalNowWhy this matters
● blocks progress16 h agoPer-source durable watermark age for this stream. Repeated writes of an identical payload do not refresh it; every required snapshotted source must terminate under policy.
● inventory progressno dataPer-source durable watermark age for this stream. Repeated writes of an identical payload do not refresh it; every required snapshotted source must terminate under policy.
● pool_metrics progressno dataPer-source durable watermark age for this stream. Repeated writes of an identical payload do not refresh it; every required snapshotted source must terminate under policy.

Coverage — live vs known

The big numbers on the site count what is live right now; the rest of the catalogue is shown here plainly rather than folded into the headline.

Pools
● 792 live (reported in 48h)   ● 255 idle (discovered, silent)
Coins
● 351 reporting hashrate (48h)   ● 112 have pools, quiet now   ● 152 listed, no pools yet

Source cross-check

Of the 666 pool–coin pairs we can measure from two independent sources (a pool’s own API and the MiningPoolStats aggregator), 57.7% agree; 242 report hashrates that differ by more than 25%. Where our sources disagree we show both and flag it, rather than silently choosing one number and presenting it as settled fact. A further 40 differ so wildly (more than 100×) that one reading is almost certainly a unit or parsing error — ours or the source’s — so we trust neither and are tracking them as data errors, not as honest disagreements.

What we do and don’t cover

Of 794 pools seen in the last 48h, 208 publish per-block detail (heights) we can show, 31 publish only an aggregate 24h block count, and 555 publish no block data at all — only hashrate and miner counts. (The directory lists more pools in total; this counts only those that returned data in the last 48 hours.) Where a pool publishes nothing for a field, we leave it blank instead of inventing a value.

When we do get something wrong, we own it: see our corrections log — a dated record of data errors we’ve published and fixed.

Live interactive directory: mining-scan.com · Pool comparisons · Algorithms