Why does the XMR monitor hashrate disagree with local RandomX?
Match the Worker name, then read the pool’s rate. If one number is missing, the address rate is unknown, not 0. CPU examples on the Kryptex page are not your monitor reading.
Compare the same Worker’s pool rate with the machine
Open Monero monitoring and read the rate by Worker name. Do not substitute network hashrate.
| The number you see | The question it answers |
|---|---|
| Live H/s in the miner | What this process claims right now. |
| Address rate on the monitor | Added only when every worker rate is a number. |
| Pool or network hashrate | The whole pool or network, not this machine. |
| Income in a revenue calculator | Needs fee and power inputs. It is not coins received. |
The monitor shows the pool’s view of each Worker
When local RandomX and the monitor disagree, name who reported the monitor’s number. Open Monero monitoring. The address rate comes from the per-worker rate Kryptex returns. The about-30-minute average is used when that field has a number; otherwise the other rate the pool sent for that worker is used. The workers are added only when every one of them has a number. If one worker has no number, the address rate is unknown and stays blank. It is not 0 H/s. A lookup does not start RandomX on your CPU and does not read the processor model.
Local, pool, network, and a calculator answer different questions
The live H/s inside the miner is that process’s own instant reading. Its window is usually shorter than the pool’s 30 minutes, so the two figures do not have to match. Kryptex labels the algorithm RandomX and describes XMRig as an open-source CPU miner for x86 or ARM, with GPUs only through plugins. The same page also has an ASIC/FPGA section, so a rate on the monitor is not “CPU only.” Kryptex states that share difficulty does not change earnings. A custom difficulty in the password field changes how often shares are submitted. It does not turn the monitor rate into XMR already posted.
Pool-wide hashrate on the Kryptex page, and the speed printed for a particular CPU, are not the monitor reading for your machine and are not today’s network hashrate. A revenue calculator that takes hashrate, electricity price, and pool fee as separate inputs, then prints estimated income and estimated profit, is a different question. This site does not estimate electricity and does not promise income.
Do not fill a missing Worker with zero
The figures below are an illustration. The address has workers named desk and nas. The pool rate for desk is 7,000 H/s and nas has no rate. The monitor does not print 7,000 for the address, and it does not print 0. Check on Kryptex whether nas is still on the list and whether its status says online or offline. If nas should not be mining XMR, remove it in the miner configuration. Do not patch the blank into 0 on the monitor. The 7,000 H/s on desk alone is still a pool rate. It does not convert into “XMR per day.”
Next step and limits
Next, match the same Worker name in the miner and on the monitor, then read that name’s pool rate. If the name does not line up, go back to which address to enter. If the status says offline and you still want a share-based reading, see accepted shares and offline. Limits: this site does not control the XMR miner, and the Agent on a Mac does not start or stop RandomX. Crash interpretation is a separate free explanation. It does not promise hashrate or income.
Common questions
Is the monitor hashrate my local RandomX?
No. It is Kryptex’s per-worker pool rate, preferring the about-30-minute average, added only when every worker has a number. One gap means unknown, not 0. This site does not start RandomX or read the CPU model.
Can Kryptex’s CPU examples stand in for my hashrate?
No. A CPU example on the pool page is not the monitor reading for your machine, and it does not stand in for the address rate.
Does a custom share difficulty raise the XMR on the monitor?
Kryptex says share difficulty does not change earnings. It changes how often shares are submitted. The monitor rate is still a pool rate, not XMR already posted.