01 What this page will show
Network figures describe the whole Spearmint chain. Pool figures describe only Spearmint Mining, one participant among however many there are. The two are never mixed in one tile.
Height, hashrate, difficulty
Current tip, estimated network hashrate over 1h / 6h / 24h windows, and the current target expressed as difficulty. Because difficulty retargets every block, the difficulty chart is effectively a hashrate chart with a one-block lag.
Recent blocks
Height, time, interval since the previous block, size, transaction count, finder (Spearmint Mining, another identified pool, or unattributed solo), coinbase transaction ID, and confirmations. Orphaned blocks shown struck through with the competing hash.
Count and versions
Reachable node count from a crawler, version distribution, and how many enforce the current consensus rules. A rising count of nodes not run by the operator is the metric that matters most.
Concentration and orphans
Share of blocks by finder over 24h and 7d, the Nakamoto coefficient (fewest finders needed to exceed 50%), and the orphan rate. These are the numbers the October 2025 meeting asked to be watched; they are published because they may look bad.
02 Where the numbers come from
- A Spearmint Core node the operator runs, queried over RPC on localhost:
getblockchaininfo,getnetworkhashps,getblock,getchaintips. The node's RPC is not reachable from the internet; a small exporter reads it and publishes JSON. - A peer crawler for node counts and version strings, which sees only nodes that accept inbound connections and therefore undercounts.
- Spearmint Mining's own share accounting for the two pool tiles, clearly labelled as such.
- Block attribution from coinbase text and published pool addresses. Anything not matched is shown as unattributed, never guessed.
Every network figure can be reproduced from your own node with the same RPC calls. If this page and your node disagree, your node is right, and the discrepancy is a bug worth reporting.
03 Recent blocks
| Height | Time (UTC) | Interval | Finder | Coinbase txid | Txs | Confirmations |
|---|---|---|---|---|---|---|
| No blocks — mainnet has not launched | ||||||
04 Pool statistics
| Figure | Meaning |
|---|---|
| Pool hashrate | Sum of accepted share difficulty over the last 10 minutes, converted to hashes per second |
| Active workers / addresses | Workers that submitted a valid share in the last 10 minutes, and distinct payout addresses among them |
| Blocks found | Count over 24h / 7d / all time, with links into the block list |
| Luck | Expected shares per block divided by actual, over the last 50 blocks; 100% is average, above is lucky |
| Pool fee | 1% of block rewards attributable to participating miners (proposed) |
| Reward methodology | PPLNS, window = 2 × network difficulty (proposed) — see how rewards work |
| Last payout run | Time, transaction ID, number of payout addresses, total distributed |
05 Data access
The same figures will be available as JSON, read-only, without authentication or rate keys, so that anyone can build a better dashboard than this one.
Responses carry a source_height so you can tell how far behind the tip the exporter was when it answered. No endpoint accepts a POST, takes an address, or returns anything about an individual miner; per-address statistics live on the mining dashboard, looked up by the address itself.
06 Questions
Why is the pool's share of hashrate shown at all?
Is the hashrate figure exact?
Will there be a full block explorer?
getblock on your own node, covers what most people need.