Read the scope before comparing numbers
Pools can estimate effective hashrate from accepted shares, which sample the work miners submit. A whole-pool figure covers all contributors to that pool. The Bitcoin network estimate covers all pools and solo miners. Bitcoin Core estimates it from recent blocks, so its window can differ from the pool dashboard’s.
- Whole pool: everyone contributing to that pool.
- Account: the combined work the pool attributes to the workers in an account or subaccount.
- Worker: work the pool attributes to one worker name. The name may represent several machines or a host’s routed allocation.
Read a sample pool dashboard
Suppose the pool shows 20 EH/s overall, your account shows 0.50 PH/s and one worker in that account shows 96 TH/s. All three readings cover the same 24 hours. The account rate is 500 TH/s, so that worker represents about 19.2% of the account’s estimated hashrate (96 ÷ 500 × 100). Before doing this calculation on your dashboard, match the start and end of the account and worker windows.
- 1 PH/s = 1,000 TH/s. 1 EH/s = 1,000 PH/s.
- Check whether the dashboard is showing an account, subaccount or worker before comparing it with the miner’s screen.
Check what the worker measures
Start with the worker that receives your miner’s work. For a direct connection, align the local and pool windows before comparing them in TH/s. Under Open Mine’s pooled routing, a pool account can receive an allocation from the provider’s fleet. Ask the host to confirm the routing and share data for the same UTC interval if the pool worker is pooled or local history is unavailable.
- If only the 15-minute pool line is low, compare a longer window such as 24 hours before judging performance.
- If the worker is missing or flat at zero, verify the pool account and worker name. Check the last accepted share and ask the host to verify routing or connectivity.
- If the gap persists, record accepted and rejected shares, their timestamps, and any restarts. Send the worker name and UTC window to support. Keep credentials private.
Work through a persistent gap
Suppose a directly connected worker averages 105 TH/s locally and 96 TH/s at the pool over the same 24 hours. The pool reading is 9 TH/s lower, or 8.6% below the local average (9 ÷ 105 × 100). This gap alone cannot tell you the cause or the share rejection rate.
- Worker: confirm the row belongs to that miner.
- Time: record both timestamps in UTC and compare the same 24 hours.
- Shares and changes: note the last accepted share, rejected shares if available, pool changes and restarts.
Compare a full-day average with an obligation
Take a 100 TH/s miner producing at that rate for 22 hours and producing zero for two. Its average over the full 24 hours is (100 × 22 + 0 × 2) ÷ 24 = 91.67 TH/s. If the target covers all 24 hours, it delivers about 91.67% of the target. If the applicable reporting rules exclude those two hours as a valid pause, the same work can meet 100% of a 22-hour obligation. The full-day average remains 91.67 TH/s.
100 TH/s rated, 91.67 TH/s over the day
One illustrative miner over 24 hours: 22 hours at 100 TH/s, then two hours at zero.
- Nominal rating
- 100 TH/sThe hardware specification
- Average over 24 hours
- 91.67 TH/s(100 × 22 + 0 × 2) ÷ 24
91.67% of a target that stays at 100 TH/s for all 24 hours.
Illustrative arithmetic, not a provider result. No catch-up, failover or share-estimation noise. Changing eligible obligation hours changes the ratio, not this 24-hour average. Open one completed UTC day
Open the Cyberian Mine delivery report and focus or hover over 3 November 2026 in the calendar. On the 4 November capture, the detail shows 80.71%: 72.27 PH/s delivered against an 89.54 PH/s obligation. Dividing the two displayed, rounded rates gives about 80.71%. The scope is 422 purchased miners and 10,128 miner-hours of obligation for that UTC day. Those hours describe the target, not time every machine was online.
- Read Delivered and Obligation together.
- Check the purchased-miner count and obligation time before comparing days.
- A cell without an obligation record is not an observed outage. Do not diagnose the cause of a low ratio from the calendar alone.
Cyberian Mine’s public November calendar, captured 4 November 2026. The selected day is 3 November UTC. Open the image and choose Actual size to read the detail on a phone. Check whether the report is an estimate
ValueHash’s public report on 4 November models how historical accepted provider ingress could serve one listed miner before any client purchase. Estimated delivery compares modeled work with its target. History coverage measures the available minute history. For 30 October 2026 UTC, the daily detail table shows 100% estimated delivery for one 136 TH/s reference miner with 96.3% of the minute history observed. Gaps contributed zero work to that calculation. Read both columns: 100% estimated delivery does not mean complete history, actual client delivery or uninterrupted operation.
Use the report to decide what to inspect next
For an available S21 XP, compare the listing’s rated TH/s and hosting terms, then open the provider’s delivery report and note which miners and UTC dates it covers. If the offer fits, use Sign in to buy to continue with that listing selected.
Open a live listing, check rated TH/s and the provider report, then sign in with the selected miner to continue.
Compare current S21 XP offers