Confirmation Latency

Overview

What it means

Confirmation latency is the elapsed time between a chosen starting event, such as broadcast, and a defined confirmation milestone. It is not one universal network number: the measurement depends on what counts as “start” and “confirmed.”

How it works

Confirmation time can include wallet signing, relay, mempool waiting, inclusion and subsequent finality or block depth. Fee settings, block intervals, validator activity and layer-two settlement policies can affect each portion. Reporting should state whether a median, percentile or maximum is used and which network and payment type were sampled.

Understanding the technical details

Measure at least broadcast-to-first-seen, first-seen-to-inclusion and inclusion-to-policy-accepted separately. A merchant will then know whether a delay comes from wallet submission, chain congestion or its own conservative policy. Report p50 and p95 alongside the sampling window; the p95 often matters more for customer support than the mean. Exclude neither stuck transactions nor failed submissions silently, because doing so produces deceptively optimistic dashboards.

Additional protocol context

Measurement should separate network latency from infrastructure latency. An explorer or indexer might report a confirmation later than a node observed it. Merchant callback delays can add another layer after the blockchain event. Recording broadcast, detection, inclusion, confirmation, and notification timestamps helps identify the actual bottleneck.

Average latency alone can hide poor user experience. Percentiles show how often transactions take unusually long. Monitoring should also segment by network, asset, fee strategy, and transaction type.

Common failures and limitations

Averages hide long-tail delays during congestion or outages. Monitoring only completed transactions introduces survivorship bias because stuck transactions disappear from the sample. Merchant support should explain which stage is delayed and whether the customer can safely take action.

Related concepts

Blockchain, Confirmation, Transaction Finality.

Further reading

Bitcoin developer guide — Transactions.