Live Network Snapshot (Last 30 Days): -
Pool Market Diversity
-
Unique Pools Actively Mining
Top Mining Pool
-
-
Top 3 Dominance
-
Blocks Mined by Top 3 Pools (%)
Mining Centralization (HHI)
-
Mining Centralization Index

Mining Pool Centralization Trend

Lower scores indicate a more decentralized and healthier pool market

Mining Power Concentration

Combined share (blocks mined) of the top 3 and top 5 powerful pools

Pool Market Share (Blocks)

Blocks mined per pool · Top 15 pools

Pool Geographic Jurisdictions

Estimated geographic spread of mining pool operations

New Pool Entries & Activity

Timeline of when pools first appeared and their current mining status

    Website

    Description missing.

    Birth (First Block Mined)
    -
    Lifetime Blocks Mined
    -
    Market Share (Last 30 Days)
    -

    Top Mining Pools

    Performance and identity breakdown of the top 30 network contributors

    Historical Pool Dominance

    Tracking the scale and share of major mining pools since 2009

    Mining Forensics & Reorg Risks

    Detecting network latency, centralization patterns, and block races

    The Investigative Framework

    We tested three hypotheses about whether mining pools hold structural advantages: anomalous streak frequency, header-first (spy) mining, and undisclosed hashrate. The five acts below follow the evidence — from incident, to mechanism test, to behavioral verdict, to coordination signals, and finally to identity fingerprints. Each signal is assessed on its own terms; where the data clears a hypothesis, that finding is stated plainly.

    Act I The Incident — Anomalous Streaks & Reorg Exposure
    Historical Record (2022 – Present)

    Consecutive Blocks & Reorg Risk

    Pools mining 7+ blocks in a row. Long streaks are rare under fair mining — this table records when they occurred and how often, as a starting point for Acts II & III.

    How to read it: This table logs anomalous mining streaks where a single pool successfully mined 6 or more consecutive blocks. It details the pool involved, the length of the streak, the exact block height it started, and the total duration it took to mine those blocks.

    Key Insights:

    • Reorg & Fork Risk: Long streaks increase the theoretical probability of block races and reorganizations — though in practice, no confirmed reorg has been attributed to pool concentration in the modern era.
    • Interpreting the propensity score: A score above 1× means more streaks occurred than the Poisson model predicts. However, the qualifying event count is typically small, so the excess often falls within random variance — especially for pools whose hashrate grew rapidly. Use it as a prompt for further investigation, not a verdict.

    How the numbers are calculated: The % era avg shown next to each pool is the block-weighted average share from that pool's first qualifying streak month through present — so each pool's baseline starts when it first became relevant, not at a common fixed date. This keeps the propensity denominator honest. The “1 in X Yrs” likelihood for each individual streak uses the pool's actual monthly hash share at the time of that event, so a streak that happened when Foundry was at 31% uses 31%, not the era average.

    Act II The Mechanism — Header-First Mining Signals
    Aggregate Profile (2022 – Present)

    Second Block Uplift

    How many times more likely a pool is to mine block N+1 after mining block N, vs. its block-weighted average hash share in that same period. Values near 1× mean the data shows no structural second-block advantage.

    How to read it: Under a fair, memoryless mining process, each pool's probability of winning any given block equals its hash share. That means P(same pool mines block N+1 | same pool just mined block N) = hash share exactly — the 1× baseline. Bars longer than 1× mean a pool converts a first block into a second block more often than chance allows.

    Methodology: The expected baseline uses each pool's block-weighted average share computed month-by-month. A pool's share at the time of each block is what sets the fair expectation — not a flat average over a multi-year window where that pool's hashrate was very different. No pool in the dataset exceeds a 1.12× lift on this basis.

    Key Insights:

    • Why pools beat 1×: Upon mining block N, a pool already holds the header and can begin hashing block N+1 immediately — while every competitor first downloads, validates, and acknowledges block N (~13 s lag). This head-start inflates consecutive win rates above the pure hash-share baseline.
    • Connecting Acts I & II: Act I showed Foundry producing more 7+ streaks than a Poisson process allows. This chart provides important context: Foundry's second-block uplift sits near 1.0×. That separation — streak frequency anomaly without a second-block signal — points to hashrate clustering (US-based miners consolidating under one pool), not header-first mining. A pool using spy-mining would show both signals simultaneously.
    • Interpreting magnitude: No pool in the dataset currently shows the second-block fingerprint of header-first mining. The ~1.11× maximum (Luxor) translates to roughly 2 extra consecutive blocks per 100 mined — within plausible random variance at that sample size.
    Second Block Lift — Per-Quarter Trend (top pools)
    Aggregate Profile (2022 – Present)

    Header-First Mining Evidence

    Time gap between consecutive same-pool blocks, broken into buckets. The sub-30s bucket is the most sensitive — a pool with an elevated rate there may be starting the next block before fully validating the previous one.

    How to read it: This chart shows the distribution of inter-block time gaps for consecutive same-pool blocks, broken into time buckets. Under a random (memoryless) mining process, inter-block times follow an exponential distribution with mean 600s — implying a natural sub-30s rate of ~4.88% and a median gap of ~416s.

    Key Insights:

    • What elevation would mean: A pool with a sub-30s rate materially above 4.88% would be starting the next block before fully receiving and validating the previous one — the header-first (spy-mining) pattern. No pool in the current dataset is above the expected baseline.
    • Timing distribution matters: Even without sub-30s elevation, an anomalously low median consecutive gap (e.g., 346s vs 416s expected) signals that a pool's second blocks are landing in the statistically fast tail more often than chance allows — a subtler but directionally important signature.
    Behavioral Verdict

    Empty Block Auditor (Behavioral History)

    Reform or persistence — since 2022 vs. last 30 days reveals who cleaned up and who doubled down.

    How to read it: The quadrant matrix plots each pool's empty block rate since 2022 (X-axis) against their last-30-day rate (Y-axis). The dotted diagonal is the "no change" reference — pools above it are getting worse, pools below it are improving. Threshold lines mark the network-weighted average.

    Quadrants:

    • 🔴 Persistent Offenders: High historically AND recently — chronic spy-miners.
    • 🚨 Newly Suspicious: Previously clean, now deteriorating — worth watching.
    • 📉 Reformed: Historically bad but recently improving — behaviour change detected.
    • ✅ Clean: Consistently low empty block rates — good network stewards.
    Historical Trend — monthly empty block rate, top offenders highlighted
    Network Verdict — Acts I & II

    Streak counts above expectation, but within plausible variance; spy-mining hypothesis not supported. Foundry USA's 7+ block streak count exceeds the block-weighted Poisson expectation — but the number of qualifying events is small, and the excess falls within random variance for a rapidly-growing pool. More importantly, their Second Block Uplift sits at baseline (~1.0×) and no pool shows a sub-30s consecutive-block rate above the expected ~4.9%. The header-first fingerprint requires both signals simultaneously; only one is present. The more likely explanation is hashrate geographic clustering — a large proportion of US-based miners routing through a single pool, producing run-length variance without the mempool-skipping signature. Empty block rates across all pools are currently near or below the network average.

    Act III Coordination Signals — Pool Transition Patterns
    Cross-pool Transition Matrix (2022 – Present)

    Who Mines After Whom?

    Each cell is the lift of pool B mining block N+1 immediately after pool A mined block N — relative to pool B's baseline hash share. Red (>1.2×) = statistically elevated hand-off; blue (<0.85×) = avoidance pattern.

    How to read it: The diagonal shows self-transitions (same pool mines both blocks N and N+1) — these are the second-block-uplift values from Act II. Off-diagonal cells reveal whether two distinct pools hand off blocks to each other more or less often than expected by their hash share.

    Key Insights:

    • Coordination clusters: Two pools consistently lifting each other's transitions suggest shared infrastructure, colocation, or merged-mining arrangements.
    • Avoidance patterns: Blue cells (lift < 0.85×) can indicate competing pools whose templates differ enough that one rarely solves the next block after the other.
    • Statistical threshold: Only pools with ≥ 5,000 blocks are shown. Pairs flagged as anomalies have lift > 1.15× and at least 200 observed transitions.

    Baseline methodology (block-weighted): Expected transitions use each pool's contemporaneous monthly hash share at the time of each block — the same approach as the Second Block Uplift chart. A pool that grew from 10% → 35% over 4 years does not get a flat 22% baseline; each block pair is weighted by the actual share in that month. This prevents fast-growing pools from appearing artificially anomalous in their early-period transitions.

    Act IV Ghost Hashrate — Do the Numbers Add Up?
    Live Alert (24h Window / 14d Baseline)

    Reported vs. Actual Hashrate (Z-Score Persistence)

    Persistent $|Z| > 2$ across multiple daily windows is the ghost hashrate signal — occasional spikes are luck, sustained elevation is evidence.

    How to read it: Each line tracks a pool's Z-Score across up to 10 daily 144-block windows (~10 days). Z-Score measures how many standard deviations a pool's block production deviates from the expectation given its market share.

    Threshold bands:

    • Red zone (|Z| ≥ 3): Statistically improbable — a single occurrence is a strong anomaly.
    • Amber watch zone (|Z| ≥ 2): Elevated — worth monitoring, not conclusive alone.
    • Persistence rule: A pool that stays in the amber or red zone across multiple consecutive windows is a "ghost hashrate" suspect.
    Act V The Identity — Block Content & Behavioral Fingerprints
    Stewardship (Last 30 Days)

    Block Efficiency Fingerprint

    Pool-level average TX count vs. block size — color reveals bytes-per-TX: green = compact fee transactions, red = inscription/Ordinals-heavy.

    How to read it: Each bubble is a pool's 30-day average. X = avg transactions per block; Y = avg block size in MB; bubble size = sample weight (blocks mined). Color encodes bytes-per-transaction: 🟢 green = compact (fee-optimizing), 🟡 amber = medium, 🔴 red = inscription-heavy.

    Fingerprint insight: Pools mining many small txs at the same block size as larger-tx pools are packing in more fee revenue per byte — a sign of active mempool management. High bytes-per-TX pools are filling blocks with witness-heavy data (Ordinals, Inscriptions).

    Stewardship (Last 30 Days)

    Average Data Overhead per Pool

    Witness bytes per transaction. BIP 110 aims to soft-limit this to 256 bytes per push.

    How to read it: Average witness-data overhead (bytes) per transaction on a log₁₀ scale. BIP 110 proposes a 256 B/tx soft-limit. The arrow (↑/↓) shows whether the pool is above or below that threshold; hover for the pool's peak single-block spike.

    Note: marapool's 5,141 B/tx average is driven by a deliberate Ordinals-mining policy — their per-block peak hit 332 kB/tx. All other pools cluster between 280–420 B/tx.

    Behavioral Consistency (2022 – Present)

    Miner Timing Patterns (Entropy Heatmap)

    Differentiating steady "Corporate" operations (Low Entropy) from irregular "Retail" mining (High Entropy).

    How to read it: Monthly coefficient of variation (CV) of inter-block arrival times since 2022 — aggregated from ~2,800 weekly snapshots. 🔴 Red = low CV (suspicious: consistent, industrial timing). 🔵 Blue = high CV (normal: irregular, retail/decentralised). The China mining ban (2021) and 4th Halving (2024) are annotated as structural inflection points.

    Why it matters: Pools with chronically low entropy operate owned hardware at industrial scale — making them uniquely capable of running the multi-block streaks in Act I. The Actor Archetypes panel below cross-references this signal with the most recent 6-month window.

    Initializing Bitcoin Mining Dashboard…