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.
| Signal | Now | Why this matters |
|---|---|---|
| ● Pool data freshness | 1s ago | How long since we last rescanned pool metrics. We flag it past 30 minutes — older than that and a number on the site may no longer match the pool. |
| ● Block stream | 38 min ago | How long since any pool reported a newly found block. A stream silent for over a day means block figures are frozen in the past, so we stop calling them current. |
| ● Live-moving pairs | 99.0% | Share of pool-coin pairs whose numbers actually changed over 24h. A source can answer 200 forever with an identical payload; only movement proves the data is live, not merely reachable. |
| ● Pools seen (48h) | 831 | Distinct pools that returned data in the last 48 hours — the breadth of what the directory currently reflects. |
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.
Of the 635 pool–coin pairs we can measure from two independent sources (a pool’s own API and the MiningPoolStats aggregator), 60.8% agree; 216 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 33 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.
Of 831 pools seen in the last 48h, 161 publish per-block detail (heights) we can show, 45 publish only an aggregate 24h block count, and 625 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