How to read KAS unpaid, paid, and the last 24 hours
Unpaid is pool accounting not yet sent. Total paid is the sum already sent. The last 24 hours is a rolling window. The page shows the three lines separately and does not publish its own total. The rolling window overlaps unpaid or paid, so adding all three counts the same stretch twice. They are not the on-chain wallet balance. The help page allows BTC or TON payouts, but this page shows the pool's KAS books only on a kaspa: account. The help page does not state a minimum payout, so that figure stays unknown. There is no daily earnings guarantee.
| One line on the page | How you can use it |
|---|---|
| Unpaid | What this wallet has not been paid. Not the on-chain balance, and not split per machine |
| Total paid | The sum already sent. Do not add it to unpaid and call that total assets |
| Last 24 hours | Accounting inside a rolling window. Not a UTC day and not a daily guarantee |
| One Worker's rate | Hashrate, not that machine's coins. The wallet books are not copied per rate |
Unpaid looks like a balance, paid looks like history, and the last 24 hours looks like today's income. On the Kaspa monitor the three lines are different books for one kaspa: wallet on the regular pool. The page shows them separately and does not publish its own total. Adding the last 24 hours together with unpaid and paid counts again the part of that rolling window already sitting in the other two lines. The address scope is in kaspa: address and pool. Rate and share difficulty are in ASIC and Worker rate.
What each line is
Unpaid is pool accounting that has not been sent. Total paid is the sum already sent. The last 24 hours rolls forward. It is not a Hong Kong or UTC calendar day, and it is not the instant of the fetch. Fetch time only says when this response arrived. See sources and freshness.
The Kaspa site says the network had no premine. It does not provide this pool's unpaid balance. KAS already in an on-chain wallet is not the same figure as pool unpaid. The API notes separate account info, payments, and rewards as things you can query. This page uses the one regular-pool account. It does not invent a second SOLO bill.
How payout coin fits
The help page says you can be paid in KAS, BTC, or TON, and it says the KAS payout fee is zero. The help page does not state a minimum payout, so this page does not say “paid once you reach X.” If the miner wallet is actually a BTC or TON address, this page does not open that account and will not show those coins as KAS unpaid.
Which branch to take
- When all three numbers exist, read them apart. Do not add the last 24 hours together with unpaid and paid, and do not divide the wallet amount by the Worker count.
- When one line is a dash, leave it unknown. Do not write 0.
- If unpaid sits still for a long time, check whether the pool still attributes the machine to this kaspa: wallet and whether you switched payout coin. Change the miner only after that check shows a mismatch. This page cannot press the pool's payout control.
- When several machines share one wallet, income is not copied. Workers the pool lists do not each take a device slot. A separately saved device does: five per project on Free, 50 on Pro. Extra sources on the same saved device do not add a slot.
An illustrative case
This is an illustration, not a bill. Suppose unpaid is 12.5 KAS, total paid is 400 KAS, and the last 24 hours is 8 KAS. The 12.5 is not the on-chain balance. Adding 12.5 and 400 is not total assets, because 400 was already sent. The 8 may overlap the 12.5, so adding it again is not two days of income. Two Workers do not turn 12.5 into 25. If the last 24 hours is missing, that cell is unknown, not 0 KAS.
Common questions
When will unpaid reach the wallet?
The help page we read does not state a minimum payout or an arrival time. This page cannot predict the next payment or start one for you. Whether it arrives on chain depends on the pool and your wallet.
Why doesn't the last 24 hours match a calendar day?
It rolls. It is not midnight to midnight in UTC or Hong Kong. Fetch time is when this response arrived. The window edges need not fall on the hour. If it is missing, do not treat it as 0.
Do two miners mean two unpaid balances?
No. Workers under one kaspa: wallet share that unpaid, paid, and last-24-hour set. The list shows each rate. It does not copy the income. Device slots count only when you save separate devices.