Why two minutes and not one
The difficulty of finding a block is recalculated as the chain advances, with the target set so blocks land about a hundred and twenty seconds apart on average. If miners arrive and blocks start coming faster, difficulty rises. If they leave, it falls. The average is the thing being defended, not any individual gap.
Monero began with a one minute target and moved to two in 2016, alongside a change to how new coin is issued. The practical effect was fewer blocks carrying more transactions each, which suits a chain where every transaction is large by design.
The figure counts as counted rather than judged because it is a stated target in consensus code rather than an observation. Measure real gaps over a week and you land very close to it, but the two is the aim and not the measurement.
The clock two minutes gives you
It turns every block count on this site into time. Ten blocks of lock is about twenty minutes. A market crediting after three confirmations is asking for about six minutes, and the six confirmation habit would be twelve. Nothing else in the section converts to minutes without this figure.
It also gives you a sense of what an ordinary wait feels like, which is mostly what stops people panicking. Four minutes of watching a screen is one or two blocks and is entirely unremarkable.
And it gives you a way to check somebody else. A claim that a payment on this chain settled in thirty seconds is not describing this chain. Turning blocks into minutes is a plain unit conversion, and the units page covers how this site handles those.
| Blocks | Expected time | What it usually is |
|---|---|---|
| 1 | About 2 minutes | The first confirmation |
| 3 | About 6 minutes | A common crediting threshold |
| 10 | About 20 minutes | The consensus spend lock |
| 20 | About 40 minutes | A cautious threshold for a large amount |
Reading two minutes as two minutes to confirmation
The common error treats the target as a delivery time. Two minutes is the average gap between blocks. Your transfer arrives at some point inside a gap, so the wait for a first confirmation runs from almost nothing up to the whole gap, and occasionally past it.
Blocks arrive on a random schedule around the average. Mining is a search and searches do not run to a timetable. A five minute gap is normal. A twenty second gap is normal. Neither means anything has gone wrong, and both will happen to you in one afternoon of watching.
The other misreading is arithmetic in a straight line. People multiply the target by the number of confirmations they want and treat the answer as a deadline. It is an expectation with a wide spread either side. Plan around the average and be unsurprised by double it.
What would change the two
A protocol change, agreed and shipped in a network upgrade. It has happened once in the life of this chain. Nothing about hardware, mining power or demand shifts the target, because the difficulty adjustment exists precisely to absorb those and hold the average where it is.
What does move without any upgrade is how full a block is. A busier chain packs more into the same rhythm, which shows up in the fee rather than in the clock. The gap between blocks stays put.
Questions people ask
Do blocks really arrive every two minutes?
On average, yes. Individual gaps are random and run from seconds to well over five minutes, which is expected behaviour rather than a fault.
Why did the target change in 2016?
It moved from one minute to two alongside a change to the emission schedule. The effect was fewer and fuller blocks.
Does a faster machine or a better connection speed this up?
No. The rhythm belongs to the network. Nothing on your side changes when the next block lands.