Local hashrate, 15 minutes hashrate, 24 hours hashrate, rejection rate

f2pool displays the status of miners for selected accounts on the “Workers” page.  This includes the miner’s average hashrate in different time units.

• Local hashrate

For GPU miners, the local hashrate displayed on the “Workers” page is the same as the hashrate displayed in the mining logs of their tools. It is the real-time hashrate that includes effective and ineffective hashrate. For ASIC miners, there is no local hashrate displayed on the “Workers” page, but miners can check it through their miner management tools and miner status page on the miners’ back-end services.

• 15 minutes hashrate

The effective hashrate that a pool receives from a miner. It displays the average hashrate from the past 15 minutes. As it fluctuates, it is a reference for a pool to check if a miner is online, but not for evaluating the performance of the miner.

• 24 hours hashrate

The effective hashrate that a pool receives from a miner. It displays the average hashrate from the past 24 hours. As it reflects mining status and stability, it is often used for evaluating miner performance. 

Usually, there is a margin of error of 5% between local hashrate and 24-hour hashrate for GPU miners--and within 3% for ASIC miners. 

• Rejection rate

Due to firmware error or excessive overlocking, shares that are submitted to a pool may be rejected. A rejection rate is the percentage of rejected shares to total shares that are submitted by the miner. 

Generally, popular cryptocurrencies have a rejection rate of around 1%. Others with smaller network hashrate and fast block addition speeds show miners with higher rejection rates.