On this page
- Block time
- A slot lasts about 400 milliseconds
- Epoch
- 432,000 slots, about two days
- Smallest unit
- 1 SOL is 1,000,000,000 lamports
- Base fee
- 5,000 lamports per signature
- Transaction lifetime
- About 150 blocks, roughly a minute
- Work limit
- 1.4 million compute units per transaction
What Solana is
A blockchain is a shared record that many independent computers keep in agreement, so that no single company can alter it. Solana is one such network. Its computers are called validators; its currency is SOL; the things recorded on it are balances, tokens and the state of programs. Anyone can read all of it, and anyone holding a private key can submit a transaction that changes the parts that key controls.
Everything is an account
Solana's state is a very large table of accounts. Each account has an address, a SOL balance, some data, and an owner: the program allowed to change that data. Your wallet is an account. A token is an account. Your balance of that token is another account. A liquidity pool is a handful of accounts.
An account must hold a small minimum SOL balance to exist, in proportion to its size. It is called rent, although it is really a deposit: it comes back when the account is closed. Solana's accounts documentation has the detail, and token accounts explained shows what this means for the tokens in your wallet.
Programs hold no data
A program is code deployed on chain, what other chains call a smart contract. On Solana, programs are stateless: the code lives in one account and all the data it works on lives in other accounts that are passed to it. One token program serves every token; one exchange program serves every pool.
This is the design choice that makes Solana fast. A transaction must list, up front, every account it will read or write. The network can therefore see which transactions touch different accounts and run them at the same time on different processor cores. Two people trading different coins do not wait for each other. Two people trading the same pool do.
Transactions and instructions
A transaction is a signed bundle of one or more instructions. Each instruction calls one program with a list of accounts and some data. Everything in a transaction succeeds together or fails together, which is what lets a swap say "take my SOL and give me tokens, or do nothing".
A transaction includes a recent blockhash as a timestamp. If it is not included in a block within about 150 blocks of that hash, it expires and can never land. This is why a stuck Solana transaction resolves itself within a minute or so, one way or the other. Solana's transactions documentation covers the format, and how to read a Solana transaction shows a real one.
Slots, leaders and the clock
Time on Solana is divided into slots of about 400 milliseconds. For each slot, one validator is the leader and is the only one allowed to produce a block. The schedule of leaders is worked out in advance for a whole epoch of 432,000 slots, about two days, weighted by how much SOL is staked with each validator. Leaders take four slots in a row.
Because everyone knows who the next leaders are, wallets and RPC nodes send transactions straight to them rather than broadcasting to the whole network and waiting. To keep validators agreed on the order of events without constant messaging, the leader runs a continuous cryptographic hash chain, called Proof of History, which works as a verifiable clock. Agreement on which blocks count is by stake-weighted voting.
When a transaction is final
| Stage | What has happened | Typical time |
|---|---|---|
| Processed | A leader put it in a block | Under a second |
| Confirmed | Validators holding two thirds of stake voted for that block | One to two seconds |
| Finalized | 31 or more confirmed blocks built on top | About thirteen seconds |
Apps usually treat confirmed as done. Exchanges and bridges wait for finalized.
What a fee is made of
Per Solana's fee structure page, a transaction pays two things:
| Part | How it is set | Where it goes |
|---|---|---|
| Base fee | 5,000 lamports per signature, fixed | Half is burned, half goes to the validator |
| Priority fee | A price you choose per compute unit, times the compute unit limit you set | All of it goes to the validator |
A compute unit measures work. A transaction may use up to 1.4 million; by default it is allowed 200,000 per instruction. The priority fee is the compute unit price in micro-lamports, multiplied by the limit, divided by a million. A worked example: a price of 500,000 micro-lamports with a limit of 200,000 units costs 100,000 lamports, or 0.0001 SOL, on top of the 5,000 lamport base fee.
Two practical points. The priority fee is charged on the limit you set, not on what you used, so a tighter limit is cheaper. And the fee is charged even when the transaction fails. Tips paid to block builders, common in trading, are separate transfers and not part of the network fee; slippage and priority fees for memecoins covers how those are chosen in practice.
Validators and clients
A validator is a server running Solana software with SOL staked to it. It takes its turns as leader, votes on other leaders' blocks, and earns fees and staking rewards. Holders who do not run a validator can delegate their SOL to one and share the rewards.
The software a validator runs is called a client. Several independent clients exist, written by different teams, which matters for resilience: a bug in one need not stop the network. RPC nodes run the same software without voting and exist to answer queries; that is what apps talk to, as the Solana RPC page explains.
Where it strains
- Hot accounts. Parallelism only helps transactions that touch different accounts. When thousands of people trade one new coin, they all write to the same accounts and queue behind each other. That is when priority fees climb.
- Dropped transactions. Under load, a leader can receive more than it can fit. Transactions that miss are not rejected with a message; they simply never appear, then expire. Apps resend until the blockhash runs out.
- Counting transactions. Validator votes are transactions too, and make up a large share of the headline transactions-per-second figure. Compare user transactions, not the total.
- History is heavy. The chain grows quickly, so ordinary nodes keep only recent history. Old transactions come from archive nodes and indexers.
- Hardware. Validators need strong machines and fast connections, which narrows who can run one compared with slower chains.
Seeing it yourself
Everything described here is visible. A Solana explorer shows live slots, leaders and any transaction. One curl request reads any account. A WebSocket subscription streams a program's activity as it happens. And for the corner of Solana where the most transactions are fought over, new tokens, a terminal such as BLIX shows the launches, trades and holders live.
More on Solana and on-chain data
This page is education about how the technology works. It is not financial advice, and nothing here recommends buying or selling anything.
Frequently asked questions
What is Solana in simple terms?
A public blockchain: a shared record of balances, tokens and program state kept by thousands of independent validators. It is designed to process many transactions in parallel and confirm them in about a second.
How fast is Solana?
A new block is produced about every 400 milliseconds. A transaction is usually confirmed in one to two seconds and finalized in about thirteen.
How much are Solana transaction fees?
The base fee is 5,000 lamports per signature, which is 0.000005 SOL. An optional priority fee is added when the network or a particular token is busy. Half of the base fee is burned.
What is a validator on Solana?
A server running Solana software with SOL staked to it. Validators take turns producing blocks, vote on each other's blocks, and earn fees and rewards.
What is Proof of History?
A continuous hash chain run by the current leader that acts as a verifiable clock, so validators can agree on the order of events without exchanging timestamps. It works alongside stake-weighted voting.
Why do Solana transactions fail or get dropped?
They fail when a condition in the transaction is not met, such as a price moving past the slippage limit. They are dropped when a busy leader cannot fit them; a dropped transaction expires after about 150 blocks and costs nothing.

