Hashrate
The number of hash verifications a mining machine can complete per second is referred to as its "hashrate." The most basic unit of hashrate is Hash/s, abbreviated as H/s.
Other hashrate units:
- 1 EH/s = 1000 PH/s
- 1 PH/s = 1000 TH/s
- 1 TH/s = 1000 GH/s
- 1 GH/s = 1000 MH/s
- 1 MH/s = 1000 KH/s
- 1 KH/s = 1000 H/s
Due to different algorithms for each cryptocurrency, the difficulty of hash operations varies between machines. Some mining machines achieve hashrates at the TH/s level, while others only reach KH/s. Therefore, comparing the hashrate of miners across different cryptocurrencies is not meaningful. To evaluate miner performance, it is necessary to compare metrics like hashrate and power consumption among machines using the same algorithm.
Local Hashrate, 15-Minute Hashrate, 24-Hour Hashrate, Rejection Rate, Latency Rate
Local Hashrate
This refers to the hashrate display for GPU miners, identical to the data shown in the mining software backend. It represents the total real-time operating hashrate of the miner, including both valid and invalid hashrate.
ASIC miners do not have a local hashrate display; their real-time and average hashrates can be viewed in bulk management tools or the miner's backend.
Local hashrate is the speed at which a miner performs hash verifications and is an indicator for evaluating the miner's computational performance. Corresponding to the local hashrate is the hashrate displayed on the mining pool (pool hashrate). The pool hashrate is calculated based on the weighted average of the number of shares (including delayed shares, excluding rejected shares) submitted by the miner to the pool within a unit of time and the task difficulty.
Pool hashrate can be categorized into 15-Minute Hashrate and 24-Hour Hashrate based on the statistical time interval. As the definition implies, the concept of pool hashrate differs fundamentally from local hashrate. Therefore, the pool hashrate usually does not match the local hashrate exactly and may be slightly lower or higher.
15-Minute Hashrate
This is the actual effective hashrate received by the mining pool from the miner, displaying the average effective hashrate over the 15 minutes prior to the view time. This metric fluctuates significantly and is mainly used as a reference for judging the miner's short-term operational status (e.g., whether it is online). It should not be used as the basis for evaluating whether the miner's hashrate meets expectations.
24-Hour Hashrate
This is the actual effective hashrate received by the mining pool from the miner, displaying the average effective hashrate over the 24 hours prior to the view time. This metric reflects the miner's operational stability and actual performance. The 24-Hour Average Hashrate is the primary basis for evaluating whether the miner's hashrate meets standards.
Generally, the margin of error between the local hashrate and the 24-hour average hashrate for GPU miners is around 5%. For ASIC professional miners, the margin of error between local hashrate and 24-hour average hashrate is within 3%.
Rejection Rate
This refers to computational results that are rejected by the mining pool upon arrival, often due to hardware errors, excessive overclocking, or other reasons. The rejection rate represents the proportion of rejected results relative to the total number of submissions. Rejection is an inherent occurrence; it can be minimized but not entirely avoided. Rejected shares are not counted towards effective hashrate.
Typically, the rejection rate for major cryptocurrencies is within 1%. However, higher rejection rates can occur for coins with low hashrate requirements and fast block times, or when miners are significantly overclocked.
Latency Rate
Delayed shares contribute to earnings, whereas rejected shares do not. Latency is primarily influenced by the miner's network connection. A good network status can significantly reduce the chance of generating delayed shares.
Transaction Hash (TXID)
A Transaction Hash, also known as TXID or Transaction ID, is the unique identifier for a transfer. A successful transfer's transaction hash is unique and immutable, so it is commonly used to query or verify that a specific transaction is genuine.
When the mining pool successfully makes a payout, the corresponding transaction hash (TXID) for that payout is displayed directly in the payment list.
- For coins mined using a mining account, the payment list is shown under "Payments" at the bottom of the "Earnings" page.
- For coins mined using login-free mining (i.e., mining directly to a wallet address), the payment list is shown under "Payments" below the hashrate chart.
In the payment record, click the "Transaction ID" for the payout you wish to query. Copy the string of characters that appears (which is the transaction hash), or click on it directly. You can then use this hash value to query the transaction on the respective coin's block explorer.
Comments
0 comments
Please sign in to leave a comment.