How Solana Processes a Transaction
A reader-friendly walkthrough of slots, leaders, and confirmation — without assuming you have read the whitepaper.
When newcomers ask how Solana “confirms” a transfer, they often picture a single computer approving the payment. The network actually rotates leadership among validators each slot, batches transactions, and propagates state updates across thousands of nodes. Understanding that rhythm helps you read block explorers and wallet pending states with less confusion.
Slots and leaders
Solana divides time into slots — short windows in which one validator acts as leader and orders transactions for its assigned slot. Leaders rotate according to stake-weighted selection. If you see a transaction marked “confirmed” in a wallet, it has been included in a block produced during one of these slots and voted on by the supermajority of stake.
Parallel execution
Unlike chains that process one transaction at a time globally, Solana’s runtime can execute non-conflicting transactions in parallel when their touched accounts do not overlap. That design choice influences how developers structure programs and why some complex DeFi actions cost more compute than a simple transfer.
What “finality” means here
Finality is the point when reversing a transaction becomes economically impractical for attackers. Solana uses tower BFT-style voting; wallets may show several confirmation levels. For everyday transfers, one confirmed state is usually sufficient. For large settlements, some readers wait for additional votes — a practice we explain in wallet security briefings rather than prescribing universally.
Reading explorers
Block explorers show slot numbers, leader identity, and program logs. Start with the transaction signature your wallet provides. Compare the slot time with your local clock to estimate propagation delay. Program logs reveal which on-chain programs interacted — useful when a swap involved multiple steps.
Further reading in our library
Our Validator & Staking Overview session covers voting mechanics in more depth. The ecosystem orientation glossary defines terms like “blockhash,” “compute units,” and “rent” that appear in explorer interfaces.