Monero Block Time and How Many Confirmations You Need

What a confirmation actually is

A confirmation is simply a block that has been added to the chain at or after the block containing your transaction. When your payment first lands in a block, it has one confirmation. Each new block mined on top of it adds another. The deeper your transaction is buried, the more work an attacker would have to redo to reverse it, which is why more confirmations mean more certainty.

On Monero the very first confirmation tells you a miner has accepted your transaction and packaged it into a block. It does not yet mean the funds are safe to treat as final, because in rare cases the newest block can be replaced by a competing one. That is the whole reason waiting for additional blocks exists.

Monero's 2-minute block time

Monero targets one new block every 120 seconds. The network adjusts mining difficulty continuously to keep that pace steady regardless of how much hashpower is online. This is slower than some chains and faster than others, and it is a deliberate balance between quick settlement and chain stability.

Because the target is 2 minutes, you can do simple math on wait times. One confirmation is about 2 minutes, 5 confirmations about 10 minutes, and 10 confirmations about 20 minutes. Real timing varies a little since blocks are found probabilistically, so sometimes a block arrives in 30 seconds and sometimes it takes four or five minutes.

Why 10 confirmations is the common standard

Monero has a built-in rule that newly mined coins cannot be spent until 60 blocks have passed, but for ordinary transactions the wallet uses a 10-block lock before outputs become spendable. That is where the familiar 10-confirmation figure comes from. Until those 10 blocks pass, your received funds show as locked and you cannot forward them.

This lock is not arbitrary. It gives the network enough time to settle on a single agreed history, which makes a deep reorganization that could undo your transaction extremely unlikely. By the time 10 blocks sit on top of yours, reversing it would require rewriting a meaningful chunk of the chain.

How many confirmations for different situations

For small everyday amounts, many people are comfortable acting on 1 to 3 confirmations because the risk of a reversal that shallow is already low. For larger amounts or anything irreversible on your end, waiting the full 10 confirmations is the sensible default and matches what most wallets enforce anyway through the spend lock.

Services that move your Monero onward, including swap interfaces, generally wait for the standard confirmation window before releasing the next leg. That is not a delay tactic, it is the network telling everyone the payment is settled and safe to build on.

Why your transaction might seem slow

If a confirmation is taking longer than 2 minutes, the most common reason is simple variance in block timing. Less commonly, a low transaction fee can cause a payment to wait for a block with free space, though Monero's dynamic fee and block size mean this is rare in normal conditions.

Another thing people notice is that the balance appears but stays locked. That is expected. The funds are there, the wallet is just respecting the 10-block lock before letting you spend them. Once the count reaches 10, the locked label clears on its own.

What this means when you swap Monero

When you swap into or out of XMR, confirmation timing is the main thing setting the pace. An incoming Monero deposit needs its confirmations to clear before the other side of the trade can be sent, and an outgoing Monero payment needs to confirm before it lands spendable in your wallet. Budgeting around 20 minutes for the Monero leg is realistic.

On MoneroSwap the process is non-custodial, so we never hold your coins while those blocks accumulate. You can swap in and out of Monero with no account and no KYC, and the wait you see is the network confirming, not funds sitting with us.

How long a Monero transfer takes from start to finish

Counting from the moment you hit send, a normal Monero transfer is visible to the recipient in under two minutes and fully settled in about twenty. The first confirmation arrives when the next block is found, which averages two minutes but is random, so it can land in twenty seconds or in six minutes. After that, confirmations arrive on a steady two-minute rhythm.

Most of the waiting people complain about is not the Monero network at all. It is the policy of whatever service they are sending to. A wallet will usually show the incoming amount as unconfirmed almost immediately, while an exchange or a swap service holds it until its own threshold is met. The chain has done its job long before the interface says so.

If you are sending to another person, one confirmation is normally enough for both of you to stop watching. If you are sending to a service, plan for roughly twenty minutes and do not be alarmed by the gap between seeing the transaction and seeing it credited.

Why Monero uses two minutes and Bitcoin uses ten

Monero originally used a sixty-second block target and moved to two minutes in March 2016. The change was made alongside a shift to a dynamic block size, and the reasoning was practical: shorter blocks mean more orphaned blocks and more overhead per unit of real transaction data, which wastes bandwidth on a chain whose transactions are already large.

Two minutes is a compromise. It settles roughly five times faster than Bitcoin while keeping the rate of competing blocks low enough that miners are not constantly discarding work. Faster is not automatically better here. A chain that produces blocks quicker than they can propagate across the network starts to fork against itself, which weakens exactly the security that confirmations are supposed to measure.

The practical consequence for you is that a Monero confirmation is worth less individually than a Bitcoin confirmation, because it represents less accumulated work. That is why the common standard is ten rather than the six Bitcoin users are used to.

The ten-block lock on your own change

There is a second reason ten shows up everywhere, and it catches people out. Monero locks every output for ten blocks before it can be spent again. This is a consensus rule, not a wallet setting, and it applies to the change that comes back to you from your own transaction.

So if you send half your balance to someone, the other half returns to you as change and is unspendable for about twenty minutes. Your wallet will often show the full balance while marking part of it unavailable. Nothing is wrong and nothing is lost. You are simply waiting out the lock.

This is why sending two transactions back to back can fail even when the arithmetic says you have enough. If you know you need to make several payments, either send them in one transaction with multiple destinations or keep some funds in outputs you have not just spent from.

How to check confirmations yourself

In the official GUI wallet, open the Transactions tab and look at the entry. It shows a confirmation count that increments as blocks arrive, and the transaction is treated as final once it passes ten. Hovering the entry gives you the transaction ID.

From the CLI wallet, the command is show_transfers, which prints height and confirmation state for each transfer. If you want to check without your wallet open at all, take the transaction ID and paste it into a block explorer, which will show you the block height it landed in and how many blocks have been found since.

A block explorer cannot show you amounts or addresses for a Monero transaction, because those are encrypted on chain. It can confirm the transaction exists and how deeply it is buried, which is all you need to answer the question of whether it went through.

What happens when the network is busy

Monero uses a dynamic block size rather than a fixed cap. When demand rises, blocks are allowed to grow, and the penalty for producing an oversized block scales gradually rather than slamming shut. The effect is that Monero does not develop the long fee auctions that congested fixed-cap chains do.

In practice this means a normal-fee Monero transaction is very rarely stuck behind higher payers. If your transaction is sitting unconfirmed for a long time, the usual causes are a wallet that has not synced, a badly chosen remote node, or a fee set manually to the lowest possible tier. Congestion is far down the list.

During genuine spikes you may see a first confirmation take longer than the two-minute average. The gap between blocks is random, and a run of slow blocks is normal variance rather than a sign of a problem.

Receiving versus sending, and why the counts differ

When you send, you care about the ten-block lock on your change and about whatever threshold the recipient applies. When you receive, you decide the threshold yourself, and the right number depends on what is at stake.

For a small payment between people who know each other, one confirmation is a reasonable place to stop worrying. For anything commercially significant, ten is the sensible default because it is what wallets, exchanges and merchant tools have converged on. Waiting longer than ten adds very little: the probability of a reorganisation that deep is negligible on a chain with Monero's hash rate.

The one case where waiting longer is genuinely wise is an unusually large amount arriving from someone you do not trust. There the extra twenty minutes costs you nothing and removes an entire category of edge case.

Misconceptions worth clearing up

A transaction with zero confirmations has not failed. It has been broadcast and is waiting for the next block. Monero also routes new transactions through Dandelion++ before general propagation, which deliberately delays how quickly the network sees them, so a brief period where an explorer cannot find your transaction is expected behaviour.

Confirmations are not a queue position and they cannot be bought past. Paying a higher fee does not get you confirmed sooner in any meaningful way on Monero, because blocks are not usually full. Fee tiers mainly affect priority in the rare case that they matter at all.

Finally, the ten-confirmation convention is a norm rather than a protocol rule. The only hard rule is the ten-block output lock. Any service is free to require more or fewer, and the number you are waiting on is a policy decision made by whoever is receiving your funds.