OnionSwap
Why Monero deposits wait ten confirmations
Send Bitcoin into a swap and one confirmation releases the payout. Send Monero and you wait for ten. The obvious reading is that the exchange trusts Monero less, or is being cautious with a privacy coin, or has simply picked a conservative number.
None of those. Ten is not a policy we chose and it is not a number any exchange can lower. It is a consensus rule in Monero itself, and the reason it exists is worth understanding — partly because it explains why no fee will speed it up, and partly because the same rule governs your own wallet in ways people misread as bugs.
The ten-block lock
Every output created by a Monero transaction is locked for ten blocks after the block containing it. During that window the output cannot be used as an input to any transaction, by anyone. Not by the recipient, not by the sender, not by a miner. The network will reject a transaction that tries.
That is the whole explanation for the wait. When your deposit lands, we have received the funds in every sense that matters — they are ours, they are visible in the wallet, nobody can take them back. What we do not have is the ability to spend them, and a payout is a spend. An exchange that advertised instant Monero deposits would either be lying or would be fronting you money from elsewhere and carrying the risk itself.
This is also why your own wallet shows a "locked" or "pending" balance after receiving Monero, and why sending a transaction can briefly leave a chunk of your balance unavailable: your change output is a new output, so it is locked for ten blocks too. Receive Monero and immediately try to forward all of it, and the wallet will tell you the funds are not spendable. Nothing is wrong.
Why the rule exists
Bitcoin has a comparable rule but applies it only to coinbase outputs — freshly mined coins are unspendable for a hundred blocks — while ordinary payments have no protocol lock at all. Monero extends the idea to every output, and the reason has to do with how its privacy works.
A Monero transaction hides which output is really being spent by signing with a ring of decoys drawn from the chain's existing outputs. The decoys are selected by an algorithm designed to mimic the age distribution of realistically-spent outputs, so that the real one does not stand out. Very young outputs are a problem for that: they are thin on the ground, unevenly propagated, and an output spent moments after creation narrows the field of plausible candidates sharply. Enforcing a minimum age gives the decoy selection a stable population to draw from and removes an entire class of timing analysis that would otherwise bite hardest on exactly the fast, automated flows an exchange produces.
It also does the ordinary job a confirmation threshold does — ten blocks of proof-of-work behind a payment makes a reorg that erases it vanishingly unlikely — but that is the secondary benefit. The lock is a privacy mechanism first, applied uniformly so that nobody's transaction is distinguishable by having opted out.
What that means in minutes
Monero targets two-minute blocks, so ten confirmations is about twenty minutes on average. Block intervals are random, so in practice a Monero-funded swap lands somewhere between roughly twelve and thirty minutes, and the spread is entirely luck rather than anything about your transaction.
Comparing confirmation counts across chains is the mistake that makes this look alarming. The counts are in different units:
One Bitcoin confirmation is about ten minutes of work. Ten Monero confirmations is about twenty. The thresholds are far closer in security terms than "one versus ten" suggests, and Monero's hashrate-per-block is not what makes the difference — the mandatory lock is.
Which is why XMR to BTC runs slower than BTC to XMR. Going in, you wait on one Bitcoin block and the Monero payout goes out immediately after; going out, you wait on ten Monero blocks. Same service, same fee, different chain rules on the deposit side.
Why a higher fee changes nothing
Fee priority buys you inclusion in a block. It has no effect on what happens after inclusion, and nine of your ten blocks are after inclusion. Even an infinite fee leaves you waiting roughly eighteen minutes.
The first block is rarely the constraint anyway. Monero's block size adjusts to demand rather than being fixed, so the persistent fee auction that defines Bitcoin's mempool mostly does not happen — under normal conditions a minimum-fee Monero transaction enters the next block. Paying more is not wrong, it is simply inert. The one situation where the fee tier matters is a genuine congestion spike, which does occur, and where the difference between the lowest and a middle tier is one or two blocks — four minutes on a twenty-minute wait.
So if your Monero deposit is slow, the fee is not the lever. Check that the transaction is in a block at all, and if it is, the remaining time is arithmetic: twenty minutes from the block that included it, give or take.
Things people mistake for a stuck deposit
The wallet says "pending" long after sending. Your outgoing transaction confirms on its own schedule, but the change output returning to you is locked for ten blocks. Wallets vary in how they present this, and several show the whole balance as unconfirmed until the change unlocks. The payment left; the display is about your change.
The balance dropped and nothing arrived. Same cause seen from the other side, usually within the first couple of minutes. It resolves itself.
A view key shows the payment but the order has not moved. Correct and expected. Watching a wallet with a view key shows received outputs, including locked ones. Seeing the deposit confirms delivery; it says nothing about spendability.
The order sits at "confirming" for fifteen minutes. That is the ten-block lock, and it is the status doing its job. The track page will move it to sending when the lock lapses.
A payment ID was requested somewhere and you did not supply one. Integrated addresses and payment IDs were superseded by subaddresses years ago, and no swap here needs one. If a service still asks, that is an ageing integration rather than something you got wrong.
Planning around it
The practical version is short. A Monero-funded swap is a twenty-minute operation, and the number is stable enough to plan on — unlike a Bitcoin deposit, where the wait is a fee market and can be much worse than the average on a bad afternoon. If the timing is what matters to you, Monero's wait is longer but far more predictable.
If you need speed on the deposit side, fund from a chain without the lock: BTC and LTC need one confirmation each, and Ethereum settles in roughly thirty seconds of block time. And if you are moving in and out of Monero repeatedly, remember the lock applies to your own change as well — batch the moves rather than making a series of small ones, or you will spend a good part of the day waiting for your own outputs to unlock.