Network — Finality Watch
Real, observed Solana confirmed→finalized latency, tracked continuously during the ongoing TowerBFT → Alpenglow consensus transition. Every number on this page is real data from this indexer's own RPC polling — never simulated or assumed.
Connecting…
Real, observed time between when this indexer's own RPC connection saw a Solana slot reach confirmed vs finalized commitment — not a canonical on-chain timestamp. Solana is mid-transition from TowerBFT consensus (~12.8s finality) to Alpenglow (~100-150ms target); this baseline is measured relative to real observed data, never a hardcoded assumption about which one is currently active. See /network for the real-time chart and anomaly history.
Real-time chart
0 real observation(s) shown in the selected window. Red dots mark observations flagged anomalous (≥3x that observation's own real trailing-hour baseline at the time it was recorded) — real source: GET /v1/network/finality/history.
Anomaly events
Real observations in the selected window whose elapsed time exceeded the real baseline that existed when they were recorded, by 3x or more.
Why this page exists
Solana is mid-transition from its current consensus (TowerBFT — a real, documented ~12.8s finality time) to a new consensus mechanism called Alpenglow, built around a new voting protocol called Votor, targeting ~150ms finality — roughly an 80-100x improvement. Per Solana's own official upgrade page, Alpenglow is not yet live on mainnet as of this writing — it's being tested on a community cluster, with mainnet activation targeted for Q3 2026, not yet confirmed.
Any bridge with a hardcoded assumption about how long finality takes (e.g. "wait for N confirmations before minting on the destination chain") could see that assumption go stale once Alpenglow activates — either unnecessarily conservative, or, during a mixed-validator-set transition period, genuinely inconsistent. This page polls Solana's own documented getSlot RPC method at both confirmed and finalized commitment and records the real elapsed time between them — relative to a real observed baseline, never a hardcoded assumption about which consensus version is currently active.
This is descriptive infrastructure context, not a claim that Bridge Radar detects or prevents any specific incident. Full API + SDK docs on /developers.