Latency

What is Latency?

Latency in blockchain refers to the total time between when a user submits a transaction and when they receive confirmation that it has been processed and included in the ledger. This encompasses network propagation, mempool waiting time, block inclusion, and any additional confirmation requirements.

Latency is distinct from throughput: a network can have high throughput (many TPS) but also high latency (slow individual confirmations), or vice versa. Both metrics matter for different use cases. Trading prioritizes low latency, while batch settlement prioritizes high throughput.

How it Works

Transaction latency comprises several components:

1. Client Processing: Wallet signs transaction (milliseconds)
2. Network Propagation: Reaches nodes/mempool (100ms-2s)
3. Mempool Wait: Awaiting block inclusion (varies widely)
4. Block Inclusion: Transaction in proposed block (block time)
5. Confirmation: Required confirmations for finality (varies)

• Bitcoin: 10 min (1 conf) to 60 min (6 conf)
• Ethereum: 12 sec (1 block) to 13 min (finality)
• Solana: <1 sec (confirmation to finality)
• Arbitrum: 250ms (soft) to 7 days (hard finality)

Practical Example

You're arbitraging a price discrepancy between two DEXs. On Ethereum mainnet, you submit your swap with high gas. It takes ~12 seconds minimum to be included in a block, plus time in mempool if congested. By the time your transaction confirms, the arbitrage opportunity may have closed. Someone with better latency captured it. On Solana or an L2 with sub-second latency, you can execute the same arbitrage before the opportunity disappears. For time-sensitive trading, latency can be the difference between profit and loss.

Why it Matters

Latency significantly impacts various blockchain applications:

• Arbitrage opportunities are latency-sensitive
• DEX order execution quality depends on speed
• MEV extraction favors low-latency participants

• Instant feedback expected by modern users
• High latency creates uncertainty and frustration
• Confirmation UX patterns vary by latency

• Interactive games need <100ms response
• Social apps need near-instant actions
• High latency breaks immersion

• Point-of-sale needs fast confirmation
• E-commerce checkout experience
• Customer willingness to wait limited

• Bridge speed limited by slowest chain
• Latency compounds across multiple hops
• Impacts capital efficiency

• Soft confirmations are fast but risky
• Final confirmations are slow but certain
• Applications must choose appropriate balance

Understanding latency helps users and developers choose networks appropriate for their use cases and set realistic expectations.