NOID confirmation differences across source snapshots
Nodes and pools observed at different times can show different confirmation counts. Chain confirmation, pool maturation and payout are separate stages. A confirmation count is not a device’s daily earnings.
What to check
Match the mainnet and exact transaction or reward block, then record the hash, source height and time. Use the relevant pool’s current maturation rules rather than applying one pool’s threshold everywhere. A lagging source should retain its age label; manually adding confirmations would conceal the actual observation.
Example
Example: a pool shows 16 confirmations while a newer node view shows 18. Check observation times and the next pool refresh. Reaching 18 in one node view does not by itself establish that the pool already paid.