How does a pool calculate my hashrate?

A mining pool estimates your hashrate by counting the valid work you send it over time. It does not read your processor’s speed directly, so its number can jump around even when your browser shows a steady rate.

Your shares are the pool’s evidence

Your hashrate is the number of mining calculations your device performs each second, usually shown as hashes per second, or H/s.

The pool cannot see every calculation you try. Instead, it gives you a target that is easier to meet than the target needed to find a Monero block. When your miner produces a result that meets the pool’s target, it submits a share: proof that your device has been doing mining work.

Most shares do not find a block. They still let the pool measure your contribution.

Each share has a difficulty, which describes how hard that target is to meet. A higher-difficulty share represents more expected work than a lower-difficulty share.

The calculation behind the number

For Monero pools, the basic estimate is:

Estimated hashrate = total difficulty of accepted shares ÷ elapsed seconds

Suppose you submit 12 accepted shares in 10 minutes, each with a difficulty of 5,000:

• Total represented work: 12 × 5,000 = 60,000 hashes.
• Time measured: 10 × 60 = 600 seconds.
• Estimated hashrate: 60,000 ÷ 600 = 100 H/s.

That does not mean your device performed exactly 60,000 calculations. Mining involves chance. You might find a share sooner or later than expected.

Pools may also use weighted averages rather than this simple calculation. That changes how quickly the displayed number responds, but the principle stays the same: accepted work divided by time.

Why pool and browser numbers differ

Your browser’s miner usually estimates speed from the calculations it performs locally. The pool estimates speed from the shares that arrive and pass its checks.

Those measurements can disagree because of:

• Luck: Shares arrive at uneven intervals, not on a fixed schedule.
• Averaging periods: A pool’s five-minute estimate can differ greatly from its one-hour estimate.
• Connection problems: Work your miner completes but never delivers cannot count as accepted work.
• Rejected shares: Invalid results or results submitted too late may not count toward the displayed accepted hashrate.
• Browser pauses: Background-tab limits, sleep mode, or closing the page can stop work while the pool’s averaging clock keeps running.

A short burst above your local speed is not proof of extra performance. A short dip below it is not automatically evidence that the pool is undercounting.

Difficulty affects how quickly the estimate settles

Many pools use variable difficulty, meaning they adjust your share target to keep submissions arriving at a manageable rate.

Higher difficulty means fewer shares at the same mining speed. Each share carries more weight, but a short-term estimate becomes less steady. Lower difficulty produces more frequent evidence of your work.

If your browser mines slowly, you may need a longer measurement period before the pool’s estimate becomes useful. Check the dashboard’s averaging period, accepted-share count, and rejection information before comparing numbers. Also check whether it shows one miner or every miner using your account.

The bottom line

A pool measures your accepted results, not your processor directly. Compare its longer-term average with your browser’s speed over the same period, and investigate persistent gaps rather than normal short-term swings.