Your miner says 100 TH/s while the pool shows 50 TH/s. That difference needs investigation, but it does not immediately prove a faulty machine or missing rewards. Start by checking whether the displays cover the same worker, units and time interval.
Match the time window before the percentages
Suppose a hypothetical miner runs at 100 TH/s for 12 hours and is off for the other 12 hours. Its simple full-day average is (100 × 12 + 0 × 12) ÷ 24 = 50 TH/s. Comparing a current running display of 100 with that 24-hour average can therefore create an apparent 50% gap without a 50% loss of work during the running hours.
Real pool estimates also have sampling variation. F2pool’s hashrate definitions distinguish its shorter online-status window from a longer performance view. Check the window actually selected on your dashboard rather than assuming “hashrate” always means the last day.
Local output and pool-accepted work are different observations
The machine reports its own running performance; the pool estimates contribution from submitted work. Shares arrive statistically rather than at perfectly uniform intervals, so a short estimate can move around even when the machine is stable. Braiins’ explanation of shares and hashrate estimates covers this distinction.
Do not compare only the number of shares when their assigned difficulties differ. The same count can represent different amounts of work. Record the pool’s effective-hashrate metric, the selected interval and any share-difficulty changes alongside a raw share count.
Read the exact status, not just the word “stale”
Accepted, stale and rejected labels can have pool-specific accounting meanings. F2pool’s same definitions explicitly distinguish a credited stale category from rejected stale shares. Do not apply a blanket “all stale work is unpaid” rule to every dashboard. Check which category your pool uses and whether its reward calculation includes it.
If a gap persists, record reject reasons and when they started. A short burst after reconnecting deserves a different investigation from continuing invalid submissions during otherwise stable running. There is no universal rejection percentage on this page that certifies a miner or a pool as healthy.
Build a small evidence log
| Record | Why it matters |
|---|---|
| Pool account and worker | A fleet total cannot be compared directly with one machine |
| Units and interval | TH/s, GH/s and different averaging windows are not interchangeable |
| Start, restart and off periods | A full-day average may include hours before the current session |
| Accepted and rejected work categories | Local computation alone does not establish credited contribution |
| Settings and error timestamps | Changes can be compared with the first persistent deviation |
For an invented fleet of four miners each running at 100 TH/s, the local running total is 400 TH/s. Comparing the pool’s 400 TH/s account total with one worker’s 100 TH/s would be equally misleading in the other direction. Identify the aggregation level before calculating a difference.
Use official troubleshooting paths without exposing access
Check the worker identity, configured pool endpoint and whether the miner reports a successful connection. Then review uptime and error logs at stable settings. The F2pool troubleshooting index separates offline miners, missing workers, connection failures and lower displayed hashrate. Follow the case matching your evidence instead of treating every mismatch as the same fault.
Do not install unsolicited firmware, disable account protection or hand over pool credentials to someone claiming to fix a dashboard. If contacting the provider, share the relevant time window and a redacted worker log. Wallet recovery phrases and private keys are never needed to compare hashrate displays.
Keep energy efficiency on a matching basis too
A measured 3,250 W divided by a simultaneous running 100 TH/s gives 32.5 J/TH. Dividing the same running power by a 50 TH/s daily average that includes downtime gives 65, but that is not a like-for-like hardware efficiency reading. Use the electricity calculator with matching running measurements and represent downtime through operating hours. For the reward side of the ledger, see PPS, FPPS and PPLNS payouts.
Educational information, not a wallet audit, transaction validation or personalised financial advice. Service support and interfaces can change. Report an error with the page URL; never send recovery phrases or private keys.