Read mining pool shares from attributed blocks
Compare pools within the same period, retain unknown blocks and separate block share from estimated network hashpower.
1. Start with the period and source
Actual mode uses public mempool.space statistics for Bitcoin mainnet. Choose a week or a month, then apply the draft. The source counts non-stale blocks by their block timestamps within its rolling window; a month is the source calendar month, not a fixed 30 days. Exact computation bounds and block heights are not supplied in this response.
Capture time records when Datisto received the response. It is neither the latest block timestamp nor confirmation that the provider’s whole index is current.
2. Shares retain the whole source denominator
Share is the pool block count divided by the total block count reported in the JSON response. Exact numerator and denominator remain in details and exports; the percentage is a rounded display. Search, pagination and comparison selection do not change this denominator. The provider X-total-count header covers a different scope and is not used.
Unknown pool identity 0 stays in the result. If row counts disagree with the reported total, the discrepancy remains visible; shares are never silently rescaled to 100%. An empty block here contains only the coinbase transaction, rather than zero transactions.
3. A pool identity is not ownership of every machine
Grouping by poolUniqueId joins only identical identities in the provider catalogue. Source-row mode retains its database poolId values. A name or similar spelling does not establish common ownership. Details retain original rows, both identities and their counts.
Attributed block share describes results within a particular window. It does not by itself establish physical ownership of hashpower, the number of independent operators or whole-network decentralization. Short windows can be sensitive to chance and are not automatically future shares.
4. Estimated network hashpower has its own window
The provider supplies three separate network estimates in H/s: based on recent block counts over 24 hours, three days and one week. Those contexts do not become monthly merely because monthly pool ranking is selected above. They derive from Bitcoin Core getnetworkhashps estimates, rather than meters on every machine.
A provider zero estimate may indicate its own failure, so it remains unknown here. This batch does not establish a pool’s hashpower, actual payouts, pool fees or profitability. Audit fields avgMatchRate and avgFeeDelta are outside this normalized view.
5. One applied result for chart and export
A period or grouping edit stays a draft until applied. Chart, table, detail and comparison retain the same applied batch and clocks. A late response from an older request must not replace a newer choice. Expired local cache remains visibly old; serving another response is not a fresh source capture.
Complete JSON and CSV include original normalized rows, the whole ranking and a shared manifest carrying the query, methodology and source proof. Search and the current page never shorten the export. SHA-256 identifies the original source response; the local result identity identifies a particular computation. Local preview does not establish public data rights.
This is a guide to Datisto. Private features require sign-in and access to your own data. Personal models use your assumptions; availability and permitted use of source data are checked with the particular result. This is not investment advice.