How Solana works: one transaction, start to finish
What happens in the second after you press send, as the network runs now. Several steps changed in October 2026, so older diagrams are wrong in places.
Your wallet signs a transaction and sends it straight to the validators scheduled to lead the next slots; the leader packs it into a block within a 200 ms slot (measured 215 ms on November 16, 2026), every other validator re-runs the block and votes, and since Alpenglow went live on 21 October 2026 a block is final once 80% of stake votes for it in one round, or 60% in two, targeted at about 150 ms. Votes are messages between validators now, not transactions.
A Solana transaction goes through five steps. Here they are in order, with what each one costs and what changed this year. Unfamiliar words are defined in the glossary.
1. Your wallet builds and signs
A transaction is a short message: the instructions to run (for example “move 10 USDC from my token account to theirs”), every account those instructions will read or write, a recent blockhash, and your signature. Naming every account up front is what lets Solana run many transactions at once later.
The blockhash is a timestamp of sorts. A transaction is only valid while its blockhash is among the last 150 blocks. At 400 ms slots that gave you about a minute; at 200 ms slots it gives you about 30 seconds (solana.com). If you sign on a hardware wallet and wait, the transaction can expire, and you simply sign again. A transaction can be at most 1,232 bytes in the legacy and v0 formats, and name up to 64 accounts.
2. It goes straight to the next leaders
Every slot has one leader: the validator allowed to produce that slot’s block. Leaders serve four slots in a row, so at 200 ms each one holds the pen for 0.8 seconds. The whole rota, the leader schedule, is computed from stake for each epoch before it starts: a validator with twice the stake gets about twice as many slots.
Because the schedule is public, your wallet’s RPC node does not wait in a shared queue. It forwards the transaction to the current and upcoming leaders directly (Solana calls this Gulf Stream). Leaders give priority to traffic from staked nodes, so many apps send through an RPC provider with stake behind it.
3. The leader orders and runs it
The leader’s scheduler picks transactions, mostly by the priority fee each one offers per unit of compute, and executes them. Two transactions that write to different accounts can run at the same time on different cores (the runtime is called Sealevel); two that write to the same account, such as the same busy trading pool, must queue. That is why a popular token launch can congest one market while the rest of the network is calm.
Each transaction pays a base fee of 5,000 lamports per signature plus its priority fee, whether it succeeds or fails (how fees work). A block now holds up to 50 million compute units: the 100-million figure set in July 2026, halved along with the slot (SIMD-0525).
Many validators run extra block-building software on top of the client, such as Jito’s bundle auction or BAM, which lets traders pay tips to have a group of transactions placed together. See MEV and Jito tips.
4. The block is spread and re-run
The leader cuts the block into small pieces (shreds) and sends them out through a relay tree called Turbine, so no single machine has to upload the whole block to everyone. Each validator rebuilds the block, re-executes every transaction and checks it gets the same result. A validator that cannot keep up falls behind and stops voting; on November 16, 2026 38 vote accounts were delinquent.
Alpenglow’s plan replaces Turbine with a single-hop relay called Rotor, but solana.com says it is “not yet scheduled”. Today’s block propagation is still Turbine.
5. Validators vote and the block becomes final
This is the step that changed on 21 October 2026.
| TowerBFT (until 21 Oct 2026) | Alpenglow, Votor (since) | |
|---|---|---|
| How votes travel | as transactions inside blocks | as messages sent directly between validators |
| Cost of voting | about 1 SOL a day per validator in fees | none; a 0.8 SOL admission ticket is burned per epoch instead |
| When a block is final | after votes stack up over 32 slots | 80% of stake votes once, or 60% votes in two rounds |
| Time to finality | about 12.8 seconds | about 150 ms targeted |
| Safety model | tolerates up to a third of stake acting maliciously | “20+20”: up to 20% malicious stake plus 20% offline |
Votes are bundled into certificates (one aggregate BLS signature that proves which stake voted), and the leader eight slots later posts them so voters get paid. A slot with no valid block gets a skip certificate instead, and the chain moves on.
Because votes no longer sit in blocks, every block is now all user transactions. That is why “transactions per second” dropped sharply on 21 October with no drop in real activity: the old figure counted votes. On November 16, 2026 the network carried about 1,771 user transactions a second (network speed keeps the series).
What about proof of history?
Proof of history was Solana’s original clock: a hash chain the leader ran to prove time had passed between events. Under Alpenglow it no longer paces block production; validators use their own local timeouts, and the chain’s timestamps come from a different source. Explainers that open with “proof of history makes Solana fast” are describing the network before October 2026.
What this means for you
For someone sending SOL or a token, Alpenglow changed nothing you have to do: wallets work as before, and a transfer is final in well under a second. Two practical effects: a signed transaction now expires after about 30 seconds if it is not sent, and a block explorer that says “confirmed” and “finalized” now means the same thing. If a transaction fails, it still pays its fee; our guide on why transactions fail covers the common causes.
Questions people ask
Does Solana still use proof of history?
Not to pace consensus. solana.com's Alpenglow page says Proof of History no longer paces block production since 21 October 2026, and tick entries left the data stream; validators use local timeouts instead. The name survives in older explainers.
How long does a Solana transaction take?
It usually lands in the next slot or two, each 215 ms on average on November 16, 2026, and Alpenglow targets finality about 150 ms after that. Under the old consensus, finality took about 12.8 seconds.
Does Solana have a mempool?
No shared public one. Wallets and RPC nodes forward transactions straight to the next scheduled leaders. Block builders such as Jito's run their own auctions for bundles, which is where most ordering games happen.
What does confirmed mean versus finalized?
Since Alpenglow, solana.com says the confirmed and finalized commitment levels describe the same state, and confirmed will be removed in a later release. Processed still means a validator has seen the transaction in a block that may not survive.
Sources
- solana.com: Alpenglow (what changed underneath, breaking changes)
- SIMD-0326: Alpenglow (votes, certificates, finality thresholds)
- SIMD-0525: Reduce Slot Times (four-slot leader window, 432,000-slot epochs kept)
- solana.com: Reduced slot times (blockhash expiry now about 30 seconds)
- Solana docs: transactions and the transaction pipeline (docs source)
- Solana docs: constants reference (150-slot blockhash age, 64 accounts per transaction)