Skip to content
Satoshi Gazette
Data DeskLabels, not ownership

Bitcoin Mining Pools: Block Share

See which pool labels appear on recent Bitcoin blocks. Use this to understand block-production concentration, not to pick the most profitable pool or identify who owns the machines.

Dated snapshot

Source served · Sep 30, 2026, 02:11 AM UTC

Snapshot dates, sources & limits +
Dated snapshotPool-label block sample

Overlapping one-week, one-month and three-month windows. Labels are not independent miners or evidence of common ownership.

Source observation
Snapshot dated
Review date
Not supplied

The snapshot is dated by the latest HTTP Date header mempool.space served in the session, the source's own clock; the counts can trail it by the cache lifetime the responses declared, which the method states, and the three windows are not an atomic chain-tip snapshot.

What am I looking at?

In the saved one-week sample, Foundry USA, AntPool, F2Pool account for 632 of 1,024 blocks: 61.72%. That is a share of observed blocks, not a measurement of hardware ownership or proof that these pools act together.

Looking for mining costs and revenue? Start with the mining desk and calculator. This page is supporting network context, not a profitability ranking.

One week

61.72%

top three labels · 1,024 blocks

One month

59.80%

top three labels · 4,575 blocks

Three months

59.90%

top three labels · 13,233 blocks

Share of blocks, not share of ownership

Each bar is the full sample. The ink segment combines the two largest labels; the accent segment is the third. The remainder includes all other labels and unattributed blocks. Names and shares are printed directly on the bar, so the reading does not depend on the colours at all.

One weekTop three: 61.72%
One monthTop three: 59.80%
Three monthsTop three: 59.90%

The windows overlap; they are not three consecutive periods or a trend line. Each percentage uses that window’s own block total. Short samples can vary with block-finding luck. Endpoints are cached independently, so these are not identical chain-tip observations. The date above is the latest HTTP Date header mempool.space served, its own clock when it answered, not a live feed or a time the source attaches to the counts.

Blocks attributed to each label

Block count · share of that window

Ordered by the one-week sample, followed by labels found only in longer windows. A dash means no row in that source response, not a verified zero. On smaller screens, each label has a record with all three windows.

Before choosing a pool

Block share cannot answer these questions. Check the pool’s dated terms and your actual hardware and account setup. This is a checklist, not a reviewed comparison or an endorsement.
Who chooses the transactions?
Who builds the block template? Can your setup choose a template, or does the pool choose for you? Ask what is supported today, not just promised.
What exactly gets paid?
Check the payout formula, pool fee, transaction-fee treatment, minimum payout and timing. Who bears block-finding luck, and what can delay payment?
Who holds unpaid bitcoin?
Check how long earnings remain with the operator, withdrawal restrictions and account requirements. A large block share is not evidence of safe custody.
Can you leave?
Check connection compatibility, failover settings, any lock-in and what happens to an unpaid balance when you switch. Do not assume switching is frictionless.

Read the number carefully

A pool label measures attributed block production in a finite rolling sample. It does not reveal who owns the connected machines, their geography, whether operators coordinate, or how quickly miners can redirect work.

Method

Calculation
For the three endpoint responses mempool.space served in one bounded session on September 30, 2026, at 02:11:53 UTC, sort labels by attributed block count and divide the first two, three, or five counts by each endpoint total. Percentages are derived at build time. The observation timestamp is the latest HTTP Date header among those responses, the source server's clock when it answered, not a time the source attaches to the counts. The responses allowed caching for up to 120 seconds, so their counts can trail that clock by as much. Independent endpoint caches can differ, and this is not an atomic chain-tip snapshot.
Attribution
mempool.space assigns pool labels from coinbase tags and known block-reward payout addresses. Its public identification repository can change, and historical blocks can be re-indexed after an identifier update.
Why it matters
A small set of labels accounts for much of this sample. That is a reason to investigate transaction selection and miners’ ability to switch, not evidence of shared ownership or coordinated policy.

Check the evidence

This desk began with the accompanying Satoshi Gazette Story. The September 3 observation is preserved separately; this refresh does not rewrite the Story’s historical figures.