Quantus hashrate is not the same figure as a block reward

A local rate is not QTC

A high local hashrate does not mean the address already has QTC. The Quantus miner repository defines quantus-miner benchmark as a measurement of CPU, GPU, or hybrid work for a duration you set. The default GPU path uses Metal on macOS. The repository states that the published CUDA and Vulkan comparisons were measured on the Linux hosts in that write-up. They are not an expected rate for Windows and not a score for your Mac. The monitor does not display those Linux figures.

The Quantus monitor does not show your machine’s H/s and does not show a network hashrate. The index supplies chain height, the count of addresses historically recorded with mining rewards, account count, and recent blocks with height, time, reward, and the block address. A sample interval exists only for consecutive heights. It describes the time gap in the blocks just fetched. It is not a protocol promise of block seconds and not your share of work. The public website describes QTC as entering circulation through proof of work and states a supply-cap narrative, plus a displayed active-miner figure. Those are statements on that site. The historical rewarded-address count here comes from the index. The two counts are not one census, and neither becomes a daily income.

The monitor has no hashrate

A reward row answers which public address the indexed mining reward was attributed to, at which height, at what time, and for what amount. The amount is still the 12-decimal conversion of the chain integer. The row does not answer how many hashes the GPU tried in that interval. If the node is not at the tip, the official guide treats locally found blocks as orphans with no valid reward, even when a benchmark looks fast. The miner pauses when the node has no peers. In that case both the live work and the reward row can be missing because the connection is down, not because the machine is too slow.

Illustrative example: you run the repository’s style of benchmark for 30 seconds and the terminal prints a local rate, while the same wormhole address has no mining-reward row on the monitor, today is 0, and lifetime is unknown or still yesterday’s figure. Both can be true together. Thirty seconds of local work does not promise a block. Do not multiply a rate by seconds and divide by a difficulty to invent QTC. This page has no such conversion, and the index used here has no difficulty field.

A fast benchmark and an empty reward list

To see whether the machine is working, read the miner log and the benchmark you ran, including duration and CPU or GPU settings. To see whether there is QTC, read the reward rows in today and lifetime and the official explorer. If the rate is high and the reward list is empty, confirm the node is Idle and the address is the wormhole from the startup log before treating the rate as income. That check is no rewards. This site does not read miner metrics and does not convert hashrate into QTC or fiat.