First confirmation
Included in a block
- With NU7 · measured
- 24s
- 25s target
- 25s
NETWORK_STATUS
Testnet · NU7 active since block #4,465,026, October 4, 2026.
Last 7 days · 25s target
Median · 2s before NU7
At the measured average pace
Daily averages. Total: 10 confirmations (ZIP 315). Earlier testnet timing was irregular.
ZIP 315 wallet policy: 3 confirmations for change, 10 for received funds.
Included in a block
Your own change can be spent (ZIP 315)
Received funds can be spent (ZIP 315)
Estimated waits. Wallet policies may differ.
Rolling 120-block average · refreshed every 15s.
Observed average unavailable · Target unavailable
Average over 120 consecutive block-header intervals. Header timestamps can move backwards. Heights are shown on the horizontal axis.
Intervals are differences between timestamps recorded in consecutive canonical block headers. They are not measurements of when this explorer received blocks. Header timestamps can move backwards; daily averages use the full time span, so such intervals cancel out.
Each bar is one complete UTC day. Today and the day containing an activation block are left out. Comparison values use the last seven days and, after an upgrade, start no earlier than its activation.
Expected waits multiply the average interval by the number of confirmations. This assumes the next block includes the transaction and that blocks arrive at random. Congestion, fees and wallet sync can add time.
ZIP 315 recommends 3 confirmations for a wallet’s own change and 10 for received funds, with no spending before 3. Wallets choose their own policy. The NU7 comparison assumes unchanged confirmation counts; ZIP 315 does not specify different counts for NU7. These thresholds are wallet policy, not a separate finality event.
Testnet allows minimum-difficulty blocks, so before NU7 its blocks did not follow the 75-second target: in the week before activation they averaged 10s with a median of 2s. Those days are faded and not used as a baseline.
Observations as of 2026-10-25 17:34:24 UTC.