Skip to main content
>

Find an address, transaction, block or Zcash name.

TOOLS

Zcash block time simulator

Pick a block time from 5 to 150 seconds and see what users would feel and what it would cost. Three confirmations take about 75s with today's 25-second blocks and about 60s at 20 seconds.
25s
Measured rangeZcash has run at 150s, 75s and 25s; the math matched each one.
5s150s
Confirmations before funds count as received

Wallets and services pick their own depth.

What users would feel

3 confirmations
75s
9 times in 10 within 2.2 min
First confirmation
25s
On average, from sending
Gaps of 2+ minutes
1 in 122
Gaps of 1+ minute: 9.1%
Longest wait, typical day
3.6 min
The slowest block gap in a day

What it would cost

Orphaned blocks
0.72%
Measured · ~25 lost races a day, late blocks excluded
Blocks per day
3,456
More headers for nodes and light wallets to process
Empty-block data
6.7 MB/day
Headers and coinbase alone, before any transactions

Why the math is trustworthy

Share of block gaps lasting 2 minutes or more. The same random-arrival model matched every speed Zcash has run at, within about a percentage point.

Gaps of 2 minutes or more: model against measured
EraModelMeasured
150s Before Blossom45.1%44.7%
75s Before NU720.3%20.7%
25s With NU70.84%0.88%
Share of block gaps lasting 2 minutes or moreRandom-arrival model curve with measured Zcash eras: 150s measured 44.7%, 75s measured 20.7%, 25s measured 0.9%.0%10%20%30%40%50%5s25s50s75s100s125s150s150s75s25s
Line: random-arrival model. Circles: measured mainnet eras. Gold: your setting. Shaded: faster than any measured era.

Compared with other chains

Protocol block targets. Chains settle differently, so only clear, documented waits are compared.

Block time (log scale)

  • Bitcoin10 min
  • Litecoin2.5 min
  • Monero2 min
  • Dogecoin1 min
  • Zcash · your setting25s
  • Cardano20s average
  • Ethereum12s slots
  • Kaspa0.1s (10 per second)

Usual wait until done

  • Bitcoin60.0 min
    6 confirmations, a common convention
  • Monero20.0 min
    10-block lock before funds can be spent
  • Litecoin15.0 min
    6 confirmations, a common convention
  • Ethereum12.8 min
    finality after two epochs (64 slots), nominal
  • Zcash at 25s75s
    3 confirmations, your choice above
Shares this exact setting.
method_and_limitationsThe model, the measured data behind it, and what it cannot tell you.

Proof-of-work blocks arrive at random. With difficulty holding the average at the target T, gaps between blocks follow an exponential distribution: the share of gaps lasting at least x seconds is e−x/T. Waiting for k confirmations is the sum of k such gaps. Because arrivals are memoryless, a transaction waits a full average gap for its first block, not half of one.

This model was checked against canonical mainnet block-header times:

  • 150s, before blossom (blocks 636,320–653,599, 17,280 gaps): average 150.68s; gaps of 2+ minutes 44.7% measured against 45.1% predicted.
  • 75s, before nu7 (blocks 3,508,000–3,543,404, 35,405 gaps): average 75.36s; gaps of 2+ minutes 20.7% measured against 20.3% predicted.
  • 25s, with nu7 (blocks 3,543,406–3,579,544, 36,139 gaps): average 25.13s; gaps of 2+ minutes 0.88% measured against 0.84% predicted.

The typical longest wait in a day is the expected maximum of a day's gaps, T × (ln n + 0.577) for n blocks. At slower targets the measured daily longest runs up to about 8% above it.

Orphans are blocks that lost a real race: a competing block that reached at least one of ZecBlock's observers no more than 2 seconds after that observer received the winning block, or that our own node adopted before switching away. Blocks arriving later everywhere are late blocks, usually a pool mining on an outdated tip; they waste work but never competed for the chain, so they are left out. Observers grew from 1 to 10 on 5 November 2026, so only the NU7 era has a comparable count: 225 orphans, 47 late blocks and 31,096 canonical blocks over the complete UTC days 7–15 November, 0.72%, about 25 a day. Live figures are on Mining. Between 10 and 25 seconds the page estimates the rate by scaling today's with block rate, assuming a fixed propagation delay; below 10 seconds orphans can rise much faster than that, so no estimate is shown. Observers do not see every competing block, so these are lower bounds.

Empty-block data multiplies blocks per day by the average size of a block holding only its coinbase transaction since NU7 (1,943 bytes). Confirmation depth is a choice: ZIP 315 recommends 10 for received funds in wallets, while many payments use fewer.

Other chains are listed at their protocol block targets. Their waits use each chain's own rule: a common confirmation convention for Bitcoin and Litecoin, Monero's 10-block lock, and Ethereum's nominal two-epoch finality, which often takes longer in practice. Proof-of-stake and blockDAG chains do not follow the random-arrival model, so they are shown for reference only.

This page shows consequences of a block time, not a recommendation. Changing it needs a network upgrade, and things the model does not cover, such as network bandwidth, mining pool behaviour and wallet sync, also matter. See measured block times on Zcash block speed.