Learn what hashrate means in the PECPool panel, how current, 1-hour, and 24-hour hashrate differ, why pool hashrate may not exactly match the miner’s local display, and how to evaluate worker and account performance correctly.
Hashrate is one of the most important values displayed in the PECPool panel. It helps miners understand how much effective mining power their workers and mining accounts are contributing to the pool.
Although hashrate may appear to be a simple number, it can change frequently and may not always match the value displayed in the local interface of an Antminer, WhatsMiner, or another ASIC device.
This guide explains how PECPool calculates hashrate, the difference between current, 1-hour, and 24-hour hashrate, how to read hashrate charts, and how to identify possible network, configuration, or hardware problems.
Hashrate is the number of cryptographic calculations a mining device can perform every second. Bitcoin ASIC miners repeatedly perform SHA-256 calculations to process mining jobs and find valid shares.
A higher hashrate generally means that the miner is performing more calculations and is expected to submit more valid shares over time.
Bitcoin mining hashrate is commonly measured using the following units:
| Unit | Meaning |
|---|---|
| MH/s | Megahashes per second |
| GH/s | Gigahashes per second |
| TH/s | Terahashes per second |
| PH/s | Petahashes per second |
| EH/s | Exahashes per second |
The hashrate of individual Bitcoin ASIC miners is commonly displayed in TH/s. Larger mining accounts or mining farms may also be displayed in PH/s.
PECPool estimates hashrate from the valid shares actually received from your workers.
The pool does not simply copy the hashrate reported by the miner. It measures effective mining performance based on real share submissions received through the PECPool stratum servers.
The general process is:
This pool-side estimate shows how much valid mining work PECPool is actually receiving from the worker.
The hashrate shown in PECPool may not always exactly match the value shown in the miner's local management interface.
This happens because the two values are calculated differently.
The ASIC miner estimates its own performance using internal chip activity, frequency, processing results, and device statistics.
Depending on the manufacturer, this may be displayed as:
PECPool estimates hashrate using valid shares received from the worker over a specific period of time.
Because the miner and the pool use different measurement methods, temporary differences are normal.
Common reasons include:
A small difference between local and pool hashrate does not automatically indicate a problem.
For a more accurate comparison, allow the miner to run continuously and review the longer pool averages instead of comparing only short-term values.
Hashrate may be displayed in several sections of the PECPool panel, including:
The displayed information may represent one individual worker, one mining account, or the combined performance of multiple workers.
Worker hashrate represents the effective mining power associated with one worker name.
A worker normally represents one physical ASIC miner when each device has a unique worker name.
For example:
myaccount.miner01
myaccount.miner02
myaccount.miner03Each worker can be monitored separately in PECPool.
Worker-level hashrate helps identify:
Account hashrate is the combined effective hashrate of all workers connected under the same PECPool mining account.
Example:
| Worker | Hashrate |
|---|---|
myaccount.miner01 |
100 TH/s |
myaccount.miner02 |
96 TH/s |
myaccount.miner03 |
104 TH/s |
The approximate combined account hashrate is:
300 TH/sSmall temporary differences may appear because each worker's pool hashrate is estimated from actual share submissions.
Current hashrate is a short-term estimate based on recent share activity.
It responds relatively quickly when:
Because it uses a shorter measurement period, current hashrate can fluctuate more than longer averages.
Current hashrate is useful for checking whether a worker is actively submitting shares at the present time.
The 1-hour hashrate represents the worker's average effective performance over a recent one-hour period.
It is smoother than current hashrate and is useful for evaluating short-term stability.
The 1-hour value can help determine:
If the miner was offline during part of the previous hour, the 1-hour average may remain lower until the measurement period contains more continuous mining activity.
The 24-hour hashrate represents a longer average of the worker's effective mining performance.
It is generally the most useful value for evaluating overall miner performance because short-term fluctuations have less effect on it.
The 24-hour average is useful for:
If a worker was offline for several hours, its 24-hour average may remain lower even after the miner reconnects and returns to normal operation.
| Hashrate Type | Measurement Style | Best Use |
|---|---|---|
| Current Hashrate | Short-term estimate | Checking immediate mining activity |
| 1-Hour Hashrate | Recent average | Checking short-term stability |
| 24-Hour Hashrate | Longer average | Evaluating general performance |
The correct value depends on what you are trying to understand.
Do not rely on only one value when troubleshooting. Review all available values together with worker status, accepted shares, last-share time, and the hashrate chart.
Short-term hashrate fluctuations are a normal part of mining.
PECPool estimates hashrate from shares, and shares are not always submitted at perfectly equal intervals.
A healthy miner may submit several shares close together and then take longer to submit the next share. This can temporarily move the current hashrate above or below the miner's expected performance.
This natural variation becomes smoother when measured over longer periods.
The PECPool hashrate chart provides a visual history of mining performance.
The chart can help identify:
A healthy chart normally contains small upward and downward movements around the expected hashrate.
A completely straight line is not required for normal mining.
A sudden hashrate drop may indicate:
A long period at zero normally means PECPool did not receive valid shares from the worker during that period.
Check whether the worker was offline, powered off, incorrectly configured, or disconnected from the network.
Repeated large changes may indicate:
A worker may appear Online because PECPool has recently received a share, while its average hashrate remains lower than expected.
Possible causes include:
Review current, 1-hour, and 24-hour hashrate together before deciding whether the miner has a persistent problem.
Zero hashrate normally means PECPool is not receiving enough recent valid shares from the worker to calculate active mining performance.
Check the following:
Accepted shares are valid pieces of mining work successfully received and approved by PECPool.
Because pool hashrate is estimated from real mining shares, accepted shares directly affect the accuracy and continuity of the displayed hashrate.
When accepted shares are increasing normally, PECPool can estimate the worker's effective performance more accurately.
When accepted shares stop arriving, the displayed hashrate will begin to fall and may eventually reach zero.
Rejected and stale shares represent work that was submitted but not accepted as valid mining credit.
Possible causes include:
A high rejected-share rate can reduce effective pool-side hashrate even when the miner reports a normal local hashrate.
When an ASIC miner restarts:
Do not evaluate long-term miner performance immediately after a restart.
A newly connected or restarted worker requires time to establish a pool connection and submit valid shares.
A practical evaluation process is:
Suppose a worker shows:
| Value | Hashrate |
|---|---|
| Current Hashrate | 103 TH/s |
| 1-Hour Hashrate | 98 TH/s |
| 24-Hour Hashrate | 71 TH/s |
This may indicate that the miner is currently operating normally but experienced downtime earlier during the previous 24 hours.
The current and 1-hour values have recovered, while the 24-hour average still includes the earlier interruption.
Suppose a worker shows:
| Value | Hashrate |
|---|---|
| Current Hashrate | 0 TH/s |
| 1-Hour Hashrate | 38 TH/s |
| 24-Hour Hashrate | 97 TH/s |
This may indicate that the miner operated normally for most of the day but recently stopped submitting shares.
Check the worker status, last-share time, pool connection, power, and miner logs.
Suppose a 100 TH/s miner shows:
| Value | Hashrate |
|---|---|
| Current Hashrate | 125 TH/s |
| 1-Hour Hashrate | 101 TH/s |
| 24-Hour Hashrate | 99 TH/s |
The high current value does not necessarily mean the miner permanently increased to 125 TH/s. It may simply have submitted several shares within a short period.
The 1-hour and 24-hour averages indicate that the miner is performing close to its expected capacity.
A short temporary drop is not always a serious problem.
Further investigation is recommended when:
Use the following process:
When several similar ASIC miners are connected under one PECPool account, compare their longer hashrate averages.
For example:
| Worker | 24-Hour Hashrate |
|---|---|
myaccount.miner01 |
101 TH/s |
myaccount.miner02 |
99 TH/s |
myaccount.miner03 |
72 TH/s |
If all three miners are the same model and operate under similar conditions, Miner 3 should be investigated because its long-term effective hashrate is significantly lower.
Different ASIC models have different rated hashrates, power consumption, cooling requirements, and operating profiles.
A worker should be compared with:
Pool-side hashrate is an estimate calculated from actual share activity. It is not expected to remain perfectly fixed every minute.
Normal short-term movement does not automatically mean that the miner, pool, or network has a problem.
The most reliable evaluation comes from combining:
| Term | Meaning |
|---|---|
| Hashrate | Estimated mining calculation speed |
| Current Hashrate | Short-term estimate of recent mining activity |
| 1-Hour Hashrate | Recent average used for short-term stability analysis |
| 24-Hour Hashrate | Longer average used for overall performance evaluation |
| Worker Hashrate | Effective hashrate of one worker identity |
| Account Hashrate | Combined hashrate of all workers under one mining account |
| Accepted Share | Valid mining work accepted by PECPool |
| Rejected Share | Submitted mining work that was not accepted |
| Last Share | Time when the most recent valid worker activity was received |
Hashrate in the PECPool panel is more than a simple performance number. It is a practical diagnostic tool that helps identify worker activity, miner stability, network quality, hardware problems, and effective mining performance.
For the most accurate assessment, review hashrate together with worker status, accepted shares, rejected shares, last-share time, and the hashrate chart.
Short-term fluctuations are normal, but persistent changes in the 1-hour and 24-hour averages should be investigated to prevent extended mining downtime or reduced effective performance.
Copyright ©2026 PECPool.