Blockchain throughput: what it is and how it works
Blockchain throughput is how many transactions a network processes in a unit of time. It differs from latency and depends on block size and consensus.

On this page
- Throughput counts committed transactions, not waiting ones.
- High throughput can keep fees lower when demand is busy.
- Block size, block time and consensus set the ceiling.
- Throughput is capacity, while latency is one transaction's wait.
That capacity has a limit. The limit comes from block size, block time and consensus rules. When demand exceeds it, users bid higher fees and confirmations slow.
What does blockchain throughput mean?
Throughput is capacity over time. For a blockchain, it is the number of transactions added to the chain in a given window. The common unit is transactions per second.
How is throughput measured?
Throughput is usually measured by counting committed transactions over a period. Networks define a transaction and a time window differently, so the count varies. Some counts include simple transfers, while others include complex calls.
Why does throughput matter?
High throughput helps keep costs low and confirmations fast when many people transact. When demand exceeds throughput, users compete by paying higher fees. That causes congestion and slower confirmations.
- Low fees when demand fits
- Faster confirmations when demand is high
- Fee bidding when demand exceeds capacity
- Waiting transactions pile up
What limits network throughput?
Blockchain architecture, block size, block time and consensus set the throughput limit. A block holds only so much data, and blocks arrive on a schedule. Consensus rules decide how nodes agree on valid blocks.
A network can raise its limit by making blocks larger or faster. That can make nodes harder to run and can affect decentralization or security.
How is throughput different from latency?
Throughput is capacity over time. Latency is how long one transaction takes to confirm. A network can process many transactions and still have high latency for each one.
Frequently asked questions
Not always. Raising throughput can make nodes harder to run or affect decentralization or security.
They often cite theoretical peak numbers from controlled tests. Those figures may count simple transfers rather than complex activity.
It can. When demand is below throughput, transactions usually confirm faster. When demand exceeds it, fees and waits rise.
Yes. Upgrades can change block size, block time or consensus rules. Real performance still depends on demand and node participation.






