Why do blockchains get congested?
Learn why shared Layer 1 resources are limited, how demand turns into fees and delays, and why scaling creates trade-offs.
On this page
Quick read
Every Layer 1 asks a shared network to validate and record limited amounts of activity. This lesson explains why growing demand turns that limit into delays and higher fees, how Ethereum measures computation with gas, and why making a chain faster always raises questions about security, decentralization, or both.
What to remember
- A base layer's capacity is bounded because every participant has to validate the same activity — the limit is the cost of a shared, checkable record.
- Fees ration that scarce capacity, so a high fee signals competition at that moment rather than a better or safer transaction.
- On Ethereum, what you pay combines how much gas the action needs with what the network charges per unit at that time.
- Refuse single-number network comparisons: a cheaper chain may have made different capacity, security, or trust trade-offs.
Why is a shared base layer limited?
A Layer 1 is not only a place where transactions appear. It is a network of participants, block producers, rules, and a shared history. To remain useful, the network needs participants to validate the same rules and agree on which activity becomes part of that history.
That work cannot grow without limit in every block. A base layer has a bounded amount of transaction data and computation it can accept at a time. When more people and applications want that space than the network can process, they are competing for the same shared resource.
What becomes scarce when demand grows?
Congestion is not one single meter. It is the practical result of several limited resources being requested at once. A simple transfer, a token action, and a smart-contract call can all compete for inclusion, even though they do not consume the same amount of computation.
| Shared resource | Why it is limited | What a busy network can look like |
|---|---|---|
| Block inclusion | A block has limited capacity for the activity it can include. | Transactions wait and compete to be selected. |
| Computation | Programs need network resources to execute under shared rules. | More complex actions can consume more of the available budget. |
| Shared history | Accepted activity becomes data the network must make available and validate. | Increasing capacity changes the cost of participating in the base layer. |
How do fees express that pressure?
On Ethereum, gas measures the computational effort required for an operation. A transaction needs network resources to execute, and the fee is paid in ETH. When many people want inclusion at the same time, the price of those resources can rise.
This does not mean a higher fee makes a transaction intrinsically better. It is a signal that demand for limited block resources is high at that moment. The amount of gas used also depends on the action: a smart-contract call can use more computation than a simple transfer.
Why is speed not just a setting to turn up?
It is tempting to treat a faster chain or lower fee as an automatic upgrade. But a base layer also needs to stay secure and open enough for independent participants to validate it. Design choices that increase throughput can change the hardware, bandwidth, coordination, or trust assumptions needed to take part.
This is the core scaling tension: a network is trying to improve capacity without casually giving up security or decentralization. There is no universal number for the “best” speed or fee; the important question is which trade-off a design makes and who must carry its cost.
What does congestion not tell you?
Congestion does not prove that a network has failed, and an empty block does not prove that a network is better. Both are observations about current demand relative to available resources. They are separate from a token's price, a project's marketing claims, or whether an application is safe to use.
Conclusion
Congestion is what scarcity looks like from a user's seat. A base layer is valuable precisely because many independent participants validate the same rules and agree on one history — and that requirement is exactly what caps how much activity a block can carry. The limit is not an oversight waiting to be patched; it is the other side of the property that makes the record worth trusting.
Because the constraint is real, fees are a rationing mechanism rather than a price list. On Ethereum, gas measures the computational effort an operation requires, and the fee is paid in ETH; when many users want inclusion at once, the price of those resources rises. A high fee therefore signals contention at that moment, not that a transaction is better, and the amount of gas consumed still depends on what the action actually does.
This is why raising throughput is a design decision rather than a setting. Choices that increase capacity can change the hardware, bandwidth, or trust assumptions required to participate in validation, which is the tension between scalability, decentralization, and security. The practical consequence for a reader comparing networks is to refuse the single-number comparison: a lower fee may reflect a different capacity or trust model, so the question is which trade-off a design has made and who carries its cost.
For a beginner, the useful mental model is simple: shared validation makes a base layer valuable, but it also makes its resources scarce. The next lessons compare different ways networks try to relieve that pressure and the new trade-offs those approaches introduce.
Frequently asked questions
More demand for a base layer's limited resources than it can process at once. A block has finite capacity for the activity it can include, so when many transactions want inclusion simultaneously they compete for the same space. Congestion is the visible result of that competition, not a malfunction.
Because the fee is effectively a bid for inclusion in a limited amount of block space. When demand rises, the fee required to be selected promptly rises with it. On Ethereum the total also depends on how much gas the action consumes, so a complex smart-contract call costs more than a simple transfer even at the same gas price.
Gas is Ethereum's measure of the computational effort an operation requires. Each action consumes an amount of gas determined by the work it performs, and the transaction pays for that consumption in ETH. Separating the amount of gas from its price is what lets a network charge for resource use rather than per transaction.
It can, but not for free. A base layer needs to stay open enough that independent participants can validate it, and design choices that raise throughput can increase the hardware, bandwidth, coordination, or trust required to take part. Raising capacity therefore shifts a cost onto someone rather than eliminating it.
It is the framing that a network is trying to improve scalability without casually giving up decentralization or security, and that pushing hard on one tends to pressure the others. It is a way of asking what a design gave up to achieve its numbers, not a proof that improvement is impossible.
No. A lower fee can reflect lower current demand, or a different capacity and trust design. It does not by itself demonstrate that two networks offer comparable security or decentralization, so a fee comparison alone is not a comparison of the networks.
No. Congestion is an observation about demand relative to available resources at a moment in time. Sustained demand can even indicate that a network is being used heavily. Equally, empty blocks do not demonstrate that a network is superior — they indicate that less activity is competing for space.
No. A higher fee improves the chance of being included sooner when there is competition for block space. It does not change what the transaction does, whether the contract it calls is sound, or whether the recipient address is correct.
Related coins
Keep learning
Recommended next reads based on this lesson.
- Why did Bitcoin need to exist?Start with the double-spend problem to understand why Bitcoin needed a shared transaction history.
- Bitcoin: the first Layer 1Learn why Bitcoin is a Layer 1 network, how its own rules secure BTC, and why settlement has trade-offs.
- Why is Ethereum programmable?See how Ethereum extended the Layer 1 idea with shared programs, ETH gas, and new trade-offs.
- Why are there so many tokens?Learn how ERC-20 made tokens reusable across Ethereum apps, and why a shared standard still leaves important risks.
