Monero 10 Confirmations: What You Are Actually Waiting For
A deposit lands, the wallet says locked, the order page says confirming. Here is what Monero's 10-block spendable age really is, measured against the chain today - and what you can do during the wait.
XMR arrives at your wallet, part of the balance is greyed out, the order page says network confirmation, and the clock keeps running. That wait is neither a mystery nor a malfunction: Monero treats an incoming output as spendable only after 10 blocks. At the protocol's 120-second block target that is about 20 minutes, and the stretch of chain we measured on 17 October 2026 took 1,327 seconds for 10 blocks - roughly 22 minutes. It is a count of blocks, not a fee auction, which is exactly why adding money to your transaction changes nothing. (how Monero fees work)
Where the number 10 actually comes from. It is a consensus constant, not a support-page policy. Monero's cryptonote_config.h defines CRYPTONOTE_DEFAULT_TX_SPENDABLE_AGE as 10 - the number of blocks after which received outputs count as spendable - and sits it next to DIFFICULTY_TARGET_V2, the 120-second block target, and CRYPTONOTE_MINED_MONEY_UNLOCK_WINDOW, the deeper 60-block lock applied to mining rewards. That is why every Monero wallet shows two balances: total and spendable, or locked and unlocked. New money lands in the first and only moves to the second after those 10 blocks. Nothing is lost. It simply is not yet spendable under the rules the network enforces.
Do not confuse it with a transaction unlock time. Monero also has a per-transaction unlock_time field, where a sender can hold a whole transaction until a future height or timestamp. That is a separate mechanism, it is rarely used, and the Monero project is deprecating its custom form at consensus alongside FCMP++. The 10-block rule is not that. It applies to every ordinary payment whether anyone asked for it or not, which is why an explorer can show a deposit as confirmed long before your wallet will let you spend it.
Why ten blocks and not one. Confirmations are a reorg discount: a block is only as final as the work stacked above it, and a chain that targets 120 seconds per block needs a deeper count than a chain with 10-minute blocks to reach the same wall-clock safety. Ten blocks is roughly 20 minutes of accumulated proof-of-work - at the difficulty we read that morning (about 7.31e11, with reported network hashrate near 6.09 GH per second) that is real committed work. Depth thresholds are conventions rather than finality gadgets: Monero has no finalised checkpoint label, so every wallet, exchange and swap service picks its own number and may change it at any time.
What the window looks like on the real chain, measured today. At 05:38:51 UTC on 17 October 2026 the network stood at height 3,785,810; at 06:00:58 UTC it had reached 3,785,820. Ten blocks in 1,327 seconds, an average of 132.7 seconds against the 120-second target - the drift is normal for a Poisson process. The block at 3,785,819 carried five transactions in 8,334 bytes, and the mempool held 28 to 45 pending transactions across our checks. Fees in that block: 1,531 bytes paid 0.00003062 XMR, 2,908 bytes paid 0.00005816 XMR, and one 2,218-byte priority transfer paid 0.00017744 XMR. With XMR around USD 558.20 that morning those are roughly USD 0.017, USD 0.032 and USD 0.099. The floor is 0.00002 XMR per kB.
Why a swap service waits for the whole count. When a provider pays out from its own inventory, that payout is final and cannot be recalled by anyone. The deposit on the other side must therefore be effectively irreversible before the payout leaves - so services wait out a full depth window rather than the two or three confirmations that a fast, high-value chain would need. In practice your order moves through stages: deposit detected, network confirmation, exchange, sending, done. That middle stretch is the 10 blocks, and the payout transaction you receive afterwards starts its own confirmation clock in your wallet. Two waits, not one.
Where the thresholds really differ. Three layers, three answers. Your wallet holds funds locked for 10 blocks because that is the protocol default. An exchange may show a deposit as credited after one or two blocks because it is writing to an internal ledger it controls - that credit is not spendable on-chain and does not survive a withdrawal. A swap or payment provider sets its own number from its own risk appetite, and can raise or lower it without notice. None of that is published consistently, and any specific number you read on a forum is a rumour until it appears in that provider's own documentation. What you can verify without trusting anyone: the deposit hash, the payout hash, and the block height each one sits in.
Six traps worth clearing. (1) Locked is not stuck - a locked balance is money the network will not let you spend yet, and it becomes spendable without any action from you. (2) Paying a priority fee to speed up a swap deposit does nothing; the block count is the clock. (3) If the XMR you hold came straight from mining, coinbase maturity applies and the wait is 60 blocks, not 10. (4) Re-sending because the first transfer seemed not to arrive is how people create double deposits and mismatched orders; the first transaction is usually just waiting for its blocks. (5) Using an exchange address as your payout address is the classic own goal - you would be handing the funds to an account whose operator decides if and when you may withdraw them. (6) Looking for a memo or payment ID on Monero is wasted effort: payments carry no memo field, and long payment IDs were removed from the protocol years ago. Subaddresses are how you keep receivers separate. (how Monero fees work)
How to spend the window instead of fighting it. Set a refund address you actually control before you send anything, and prefer a fixed quote: the rate locks at order creation, so 20 minutes of market movement is not your problem. Run one small test swap before a large one so the address and network choices are proven. Budget 25 to 40 minutes end to end for a Monero leg, split larger sums into tranches instead of one giant order, and check both transaction hashes on the order page against a block explorer when they appear. If Tor matters to you, the mirror is at 4jyoxqdyx7dh3xfjctihpld7fgliowhimajfszcgypxash5rjqhas3yd.onion. Live reference at the time of writing: 0.01 BTC quoted 1.43172703 XMR and 1 XMR quoted 541.934556 USDT, with spot XMR near USD 558.20 that morning - the quote on the page governs, and the catalog we measured carried 538 assets across 72 networks. (how Monero privacy works)