Why is my pool hashrate different from my local XMRig hashrate?

Your pool hashrate and your local XMRig hashrate measure the same mining work in different ways. XMRig measures how fast your computer is working, while your pool estimates your speed from the work you send it. Short-term differences are normal; a large gap that lasts needs a closer look.

Your miner measures speed; your pool estimates it

A hash is one attempt to solve the mining puzzle. Your hashrate, shown in hashes per second (H/s), tells you how many attempts your computer makes.

XMRig, the mining program running on your computer, measures those attempts directly. Its speed readings usually cover several periods, such as 10 seconds, 60 seconds, and 15 minutes.

Your pool cannot see every attempt. Instead, you send it shares: results that prove you have done mining work. Shares meet an easier target than the one needed to find a real Monero block.

The pool estimates your hashrate from the difficulty of your accepted shares and how often they arrive. That makes its number an estimate, not a direct reading of your processor.

Share luck makes the pool number bounce

You do not find shares at perfectly regular intervals. Even with steady local speed, you might submit several close together, then wait longer for the next one.

That randomness can make your pool report:

• More than XMRig: You found shares faster than expected during that period.
• Less than XMRig: You had a slower run of share discoveries.
• Zero briefly: No shares arrived within the pool’s short measurement window.

A higher share difficulty, meaning a harder target for each share, usually means fewer shares with more work credited to each. That can make a short-term estimate especially uneven on a slower computer.

Check the dashboard’s averaging period. A five-minute pool estimate is not a fair comparison with XMRig’s 15-minute average. After starting or restarting, allow at least a full pool measurement window to pass. Several hours of steady mining can give you a more useful comparison.

Look for work the pool is not counting

If the pool stays noticeably below your local speed, check XMRig’s messages and the pool’s accepted and rejected share statistics.

Possible causes include:

• Rejected or stale shares. Rejected shares were not accepted. Stale shares arrived after their mining job was no longer current. Whether they receive credit depends on the pool’s rules.
• Connection interruptions. Your computer may show a local speed even while communication with the pool is disrupted.
• Restarts or pauses. The pool’s average may include downtime that your current local reading does not.
• Developer donation time. XMRig can briefly mine for its developers. That work does not go to your chosen pool account.
• The wrong dashboard view. You may be comparing one worker with an account total, or viewing a different wallet address.

Ordinary pool fees usually reduce your payout rather than explain a lower reported hashrate. Check how your pool labels its figures.

The bottom line

Compare matching time periods after a steady mining session, and focus on accepted shares rather than individual dashboard jumps. If the gap remains large, check connection errors, rejected shares, downtime, and your wallet and worker settings. A temporary difference is usually share luck—not proof that your computer is slower or your pool is cheating.