A mining pool ranking page looks simple: a list of pool names, a percentage, and sometimes a number of blocks. In practice, it is a backward-looking record of blocks observed during a selected period, combined with pool attribution based on public evidence. The resulting block share is often used as a proxy for a pool's share of network hashrate, but it is not a live inventory of ASICs, not a measurement of who owns the underlying mining hardware, and not a statement about payout quality. Misreading these distinctions leads to common errors: treating a pool's ranking-page share as its share of global hardware, comparing numbers measured over different time windows, or assuming that a larger ranking position means a larger BTC payout. This article separates the concepts that ranking pages tend to place next to each other, using a public Mempool dashboard snapshot as a worked example.
What a Ranking Page Actually Measures
Bitcoin's own mining documentation draws a clear line between the shares a pool uses internally to measure each miner's submitted work and the much rarer shares that also meet the network target (Bitcoin Developer Guide: Mining). Public ranking pages, hosted by explorers or analytics sites rather than the pool itself, generally do not see a pool's internal share records, worker list, or hardware inventory. Instead, they observe blocks recorded in the provider's indexed main chain and attempt to attribute those blocks to mining pools using public on-chain evidence.
From there, a ranking page may show the number of attributed blocks and the corresponding block share for the selected period. If the provider also publishes an estimated pool hashrate or hashrate share, that figure is a statistical estimate derived from observed mining outcomes over time rather than a direct measurement of connected machines.
Four Fields to Check Before Interpreting Any Number
Before drawing a conclusion from a ranking page, identify four things: the network and coin being ranked, the data provider, the selected time window, and whether the displayed metric is blocks found, block share, estimated hashrate, or a combination of these. These fields are often shown in small text near a dropdown menu, and skipping them is one of the most common causes of misreading a ranking table.
Why the Time Window Changes the Picture
A one-day ranking and a one-week ranking answer different questions, and they are not interchangeable. Because block discovery is probabilistic, a pool's observed block share over a small number of blocks fluctuates more than its share over a larger sample. On Mempool, for example, changing the ranking window from one day to one week changes both the number of observed blocks and the sample used to calculate each pool's displayed share.
A noticeable difference between a 24-hour figure and a seven-day figure does not, on its own, indicate that miners joined or left the pool. Part of the difference may simply reflect normal variance in block discovery. Comparing a 24-hour figure for one pool against a one-month figure for another pool is even more misleading because the two figures come from different sample periods.
Blocks Found and Block Share Are Linked, but Estimated Hashrate Is a Separate Layer
A Mempool mining dashboard snapshot taken on September 2, 2026 listed 1,031 total blocks in its one-week ranking, with Foundry USA attributed 273 blocks (26.48%), ViaBTC attributed 80 blocks (7.76%), and 14 blocks (1.36%) left unattributed. These percentages are observed shares of the total block count: 80 divided by 1,031 equals 7.76%, and 273 divided by 1,031 equals 26.48%. When a page shows both an attributed block count and a percentage share for the same window, those two figures are different presentations of the same underlying block observation.
The same dashboard displayed a one-week estimated network hashrate of 918.84 EH/s for that period. That network-level estimate should be kept separate from the pool's observed block share. A ranking-page percentage is useful as an indicator of recent mining activity, but it should not be treated as a direct reading of a pool's connected hashrate or hardware inventory. The miners contributing to a pool can include independent operators, hosting customers, and proprietary operations, so recent block production does not tell readers who owns the underlying machines.
Pool Attribution Has Limits
Public ranking pages need a method for deciding which pool mined each block. Mempool's own mining-pools repository states that its pool definitions use coinbase tags and payout addresses to match blocks to known pools (Mempool mining-pools repository). This means attribution depends on the public identifiers available to the data provider.
Other explorers use similar methods. Blockchain.com's methodology for its pool-distribution chart describes pool attribution as an estimation process and notes that when a pool changes its identifying tag or addresses, its labelled contribution can decrease while the "Unknown" category increases (Blockchain.com pool distribution methodology). In the Mempool snapshot above, the 1.36% Unknown share reflects blocks the dashboard could not confidently assign to a known pool under its attribution rules. It is a limitation of public attribution data, not evidence of a network anomaly or malicious activity. Readers should avoid assigning an Unknown share to any specific named pool without direct evidence.
Explorer Rankings, Pool Dashboards, and ASIC Displays Measure Different Things
A ranking page, a pool's own worker dashboard, and a miner's local ASIC interface can all show hashrate-related figures at the same moment and still disagree, because each measures a different scope over a different window. ViaBTC's help documentation states that its real-time hashrate is calculated based on the average hashrate of the last ten minutes, while its daily hashrate statistics represent the average hashrate of the previous 24 hours (ViaBTC: why pool and miner hashrate can differ). A miner's local display, by contrast, may use its own refresh interval and averaging method set by the hardware vendor.
These figures measure different scopes and should be interpreted according to the question being asked. A temporary gap between a device's local reading and a pool's dashboard figure does not automatically indicate rejected shares or hardware failure; it may simply reflect different averaging windows. If the gap is large or persistent, factors such as network latency, rejection rate, firmware compatibility, and hardware settings should also be checked. The same distinction applies to a public explorer's estimated hashrate: it is a trailing statistical estimate based on network observations, not a live reading of every machine connected to a pool.
Ranking Position Does Not Determine Miner Payouts
A pool's position on a ranking page reflects recent block production and, by extension, provides an indicator of its recent share of network mining activity. It does not describe payout method, fee structure, or realized revenue. Since Bitcoin's fourth halving on April 20, 2024, at block 840,000, the block subsidy has been 3.125 BTC per block, with transaction fees added on top and varying from block to block. Because fee income differs across blocks, a pool that finds a certain share of blocks in a given period does not necessarily receive the same share of total BTC revenue in that period, and how that revenue is split among individual miners depends further on the pool's payout calculation method and fee rules. These are accounting questions that belong to a pool's own statistics pages and payout documentation, not to a public block-ranking table.
A Practical Checklist for Reading Ranking Pages
When reviewing a mining pool ranking page, consider the following before drawing conclusions:
- Confirm the coin, the data provider, and the exact time window shown for the figures.
- Check whether the page displays attributed blocks, block share, estimated hashrate, or a combination of these metrics.
- Compare pools only within the same time window; avoid mixing a 24-hour figure with a weekly or monthly one.
- Treat an "Unknown" category as an attribution gap, not evidence about a specific pool or an unusual event.
- Remember that a pool's own worker dashboard, a device's local hashrate reading, and a public ranking page are separate measurements with separate scopes.
- Do not use a ranking-page percentage to estimate payout amounts, hardware efficiency, or profitability; review the pool's payout method and fee documentation for those questions.
FAQ
Does a pool's ranking-page share mean it controls that percentage of Bitcoin's mining hardware?
No. The displayed share reflects the pool's portion of blocks attributed to it during the selected window and is commonly used as an indicator of its recent share of network mining activity. The miners contributing to that share can include independent operators, hosting customers, and proprietary fleets, and the figure says nothing about who owns the underlying hardware.
Why do a pool's 24-hour and 7-day rankings sometimes look very different?
Block discovery is probabilistic, and a 24-hour window contains far fewer observed blocks than a 7-day window. A smaller sample naturally produces more variation in the displayed block share, even without any real change in the pool's connected miners.
What does "Unknown" mean on a pool ranking chart?
It indicates that the dashboard's attribution method — for example, matching coinbase tags or known payout addresses — could not confidently assign that block to a specific pool. It is a data-attribution limitation, not evidence of unusual network activity.
Can I use a pool's ranking position to estimate my own mining payout?
No. Ranking position describes recent block production at the pool level. Individual payouts depend on the pool's payout method, fee structure, valid and rejected shares, and settlement rules, which are separate from the public ranking figures.
Why might my miner's local hashrate reading differ from the pool's dashboard figure?
The two are typically calculated over different time windows using different methods — for example, ViaBTC calculates real-time hashrate based on the average of the last ten minutes and daily statistics over the previous 24 hours, while a miner's local interface may use a much shorter refresh interval. A short-term difference does not necessarily indicate a problem.