A Monero-to-Bitcoin swap can take around 20 minutes just for a newly received Monero output to become spendable, because Monero applies a 10-block age requirement and targets a two-minute block interval. That is a protocol estimate, not a promised swap time: deposit detection, a service’s settlement policy, Bitcoin confirmation, and either chain’s congestion can add more.
Which clock is holding up the swap?
The first delay to check is Monero’s output spendability, not the number of Bitcoin confirmations. After a normal incoming output is included in a Monero block, consensus prevents it from being spent until it has aged 10 blocks; at the nominal interval, that is roughly 20 minutes from inclusion.
For someone moving funds into a Bitcoin-only app, a Monero bridge is the cross-chain route that turns the XMR deposit into BTC in one flow. The timing question is still chain-specific: the Monero side must be observed and accepted, while Bitcoin settlement has its own confirmation behavior.
The 20-minute figure is only a planning baseline. Monero’s two-minute interval is a target, not a timer, so actual block spacing varies; the age count also starts at inclusion, not when you press send. A transaction waiting in the mempool has not started that clock.
What do the key timing checks tell you?
- Monero inclusion: Has the deposit entered a block?
- Monero age: Has the output cleared its 10-block spendability lock?
- Bitcoin settlement: Has the destination transaction been broadcast and confirmed?
Inclusion proves that the network has recorded the transaction, but it does not mean the received output is immediately spendable. If a swap service needs to spend that output to settle a trade, the age lock can matter directly; the service may also use inventory or a different settlement arrangement, so the lock alone does not reveal its policy.
The 10-block rule is separate from a service’s deposit acceptance threshold. A service can wait for its chosen risk threshold before treating a deposit as settled, and a reorganization can undo recent blocks. Do not assume “10 confirmations” is a universal bridge setting: check the actual status and terms for the route you use.
On the Bitcoin side, the transaction can be broadcast before it has a confirmation, but the receiving app may require one or more blocks before crediting it. Bitcoin targets a 10-minute block interval, so a single confirmation often adds around 10 minutes on average; congestion and the transaction’s fee rate can make the wait shorter or longer.
How should you estimate the total time?
Break the wait into stages rather than multiplying one chain’s block time by a confirmation count. A useful estimate is: time until Monero inclusion, the remaining Monero age requirement if the service must spend the output, any additional acceptance or settlement wait, then the Bitcoin broadcast and the destination app’s confirmation requirement.
For example, suppose your deposit is included quickly and the route waits for the XMR output to become spendable. Budget roughly 20 minutes for Monero’s 10-block age, then allow for the service’s settlement and about 10 minutes per Bitcoin confirmation the receiving app requires. These are illustrative averages, not a guaranteed completion window.
If your Monero wallet shows the transfer as locked, that is consistent with the age requirement; it does not by itself mean the swap failed. If the transaction is still unconfirmed, focus on Monero inclusion first. Once the route reports that the BTC transaction has been sent, inspect that transaction’s confirmation state rather than continuing to troubleshoot the XMR deposit.
What should you choose for an app deadline?
If the destination app needs confirmed BTC by a deadline, allow slack for both chains and the settlement policy; a tight 30-minute window is risky even when the nominal estimate looks close. The route’s stated completion estimate and the receiving app’s crediting rule matter more than the 20-minute protocol baseline.
monerobridge.org lets you move and swap crypto across chains in one flow, which is a practical option when the immediate task is turning XMR into BTC for another app. I would check the destination asset and its confirmation requirement before starting, then avoid scheduling the next action around a single average block interval.
One practical tip: record the Monero transaction ID and check whether it is included before treating a slow swap as a service issue; that quickly separates a pending deposit from a later settlement delay.