Chain growth · execution layer

Monad is scaling. Is the parallelism holding?

Transaction counts are easy to find. What nobody tracks is whether a growing chain keeps the parallelism it was designed for. pev traces every block, so we can watch throughput, the number of contracts actually running, and execution health together.

Window7d30d90dall (123d)pev has indexed from 2026-04-25 · 137d of chain history
37.0M
transactions traced
7-day window
2.0M
blocks analyzed
1,996,372 total
1.8M
addresses tracked
in pev's index
Throughput

More transactions, every week

+9.4% first half vs second
5,427,638 transactions2026-09-025,427,638 txs · 285,693 blocksscore 75.7 · 18.07 conflicts/block
5,053,938 transactions2026-09-035,053,938 txs · 286,160 blocksscore 72.3 · 18.73 conflicts/block
4,847,428 transactions2026-09-044,847,428 txs · 285,095 blocksscore 71.8 · 16.31 conflicts/block
4,880,790 transactions2026-09-054,880,790 txs · 284,127 blocksscore 75.8 · 14.1 conflicts/block
5,239,594 transactions2026-09-065,239,594 txs · 284,121 blocksscore 74.4 · 15.51 conflicts/block
5,854,714 transactions2026-09-075,854,714 txs · 285,418 blocksscore 74 · 20.31 conflicts/block
5,682,378 transactions2026-09-085,682,378 txs · 285,758 blocksscore 75.7 · 18.09 conflicts/block
transactions per day2026-09-022026-09-08
Execution health

Does the parallelism hold?

conflicts per block +1.5%
75.7 /100 parallelism score2026-09-025,427,638 txs · 285,693 blocksscore 75.7 · 18.07 conflicts/block
72.3 /100 parallelism score2026-09-035,053,938 txs · 286,160 blocksscore 72.3 · 18.73 conflicts/block
71.8 /100 parallelism score2026-09-044,847,428 txs · 285,095 blocksscore 71.8 · 16.31 conflicts/block
75.8 /100 parallelism score2026-09-054,880,790 txs · 284,127 blocksscore 75.8 · 14.1 conflicts/block
74.4 /100 parallelism score2026-09-065,239,594 txs · 284,121 blocksscore 74.4 · 15.51 conflicts/block
74 /100 parallelism score2026-09-075,854,714 txs · 285,418 blocksscore 74 · 20.31 conflicts/block
75.7 /100 parallelism score2026-09-085,682,378 txs · 285,758 blocksscore 75.7 · 18.09 conflicts/block
parallelism score (0-100)2026-09-022026-09-08
18.07 conflicts per block2026-09-025,427,638 txs · 285,693 blocksscore 75.7 · 18.07 conflicts/block
18.73 conflicts per block2026-09-035,053,938 txs · 286,160 blocksscore 72.3 · 18.73 conflicts/block
16.31 conflicts per block2026-09-044,847,428 txs · 285,095 blocksscore 71.8 · 16.31 conflicts/block
14.1 conflicts per block2026-09-054,880,790 txs · 284,127 blocksscore 75.8 · 14.1 conflicts/block
15.51 conflicts per block2026-09-065,239,594 txs · 284,121 blocksscore 74.4 · 15.51 conflicts/block
20.31 conflicts per block2026-09-075,854,714 txs · 285,418 blocksscore 74 · 20.31 conflicts/block
18.09 conflicts per block2026-09-085,682,378 txs · 285,758 blocksscore 75.7 · 18.09 conflicts/block
conflicts per block2026-09-022026-09-08

This is the pair that matters. Throughput can grow while the chain quietly does more duplicate work: every conflict is a transaction Monad executed, threw away, and ran again. Watching the two together is the only way to tell real scaling from busywork.

Parallel execution

How many waves does a block need?

avg 4.82 waves

Monad executes a block in waves: everything that can run together runs together, then whatever was blocked runs next. One wave means perfect parallelism. This is what the score is actually made of, it's 100 × (1 − waves / stateful txs), so wave depth is the parallelism.

1 wave21.3%
2 waves24.8%
3 waves20.0%
4 waves13.2%
5 waves7.8%
6 waves4.7%
7 waves2.8%
8 waves1.7%
9 waves1.1%
10 waves0.7%
11 waves0.5%
12 waves0.4%
4.772026-09-025,427,638 txs · 285,693 blocksscore 75.7 · 18.07 conflicts/block
5.032026-09-035,053,938 txs · 286,160 blocksscore 72.3 · 18.73 conflicts/block
4.892026-09-044,847,428 txs · 285,095 blocksscore 71.8 · 16.31 conflicts/block
4.22026-09-054,880,790 txs · 284,127 blocksscore 75.8 · 14.1 conflicts/block
4.712026-09-065,239,594 txs · 284,121 blocksscore 74.4 · 15.51 conflicts/block
5.32026-09-075,854,714 txs · 285,418 blocksscore 74 · 20.31 conflicts/block
4.862026-09-085,682,378 txs · 285,758 blocksscore 75.7 · 18.09 conflicts/block
average waves per block2026-09-022026-09-08
Where the contention lives

Ten storage slots, most of the problem

3d sample
44.2%of all slot-level contention on Monad concentrates in these ten storage slots. Contention isn't spread across the chain, it pools.
1ShMonad (shMON)slot 0x000000002.4M
2ShMonad (shMON)slot 0x000000002.4M
3ShMonad (shMON)slot 0x000000002.4M
4ShMonad (shMON)slot 0xd9f18d9a2.4M
5Perplslot 0xd98b3c101.9M
6Perplslot 0xc824469a1.2M
7Perplslot 0xca841faa1.1M
8USDC (USDC)slot 0xd17580f9657K
9Perplslot 0x482471ad590K
10Kuru Exchange: MarginAccountslot 0xaad6be10540K

Share of slot-attributed conflicts, measured, not projected. A single conflict can involve more than one slot, so this is each slot's share of all slot-level contention rather than of the block conflict count. We deliberately don't claim what the parallelism score would become if these were fixed: the score derives from wave depth, and how removing a conflict collapses a wave depends on the rest of the block.

Block capacity

How full are Monad's blocks?

7d with gas data
10.4%of the available block gas is being used. Headroom is what a chain has left before contention starts costing real throughput.
12.27 % of gas limit2026-09-025,427,638 txs · 285,693 blocksscore 75.7 · 18.07 conflicts/block
10.2 % of gas limit2026-09-035,053,938 txs · 286,160 blocksscore 72.3 · 18.73 conflicts/block
8.01 % of gas limit2026-09-044,847,428 txs · 285,095 blocksscore 71.8 · 16.31 conflicts/block
9.27 % of gas limit2026-09-054,880,790 txs · 284,127 blocksscore 75.8 · 14.1 conflicts/block
10.18 % of gas limit2026-09-065,239,594 txs · 284,121 blocksscore 74.4 · 15.51 conflicts/block
12.09 % of gas limit2026-09-075,854,714 txs · 285,418 blocksscore 74 · 20.31 conflicts/block
10.82 % of gas limit2026-09-085,682,378 txs · 285,758 blocksscore 75.7 · 18.09 conflicts/block
block gas used, % of limit2026-09-022026-09-08

Gas capture started when this column was added, so this series begins later than the rest of the page. Re-executed transactions are absorbed by the chain, not billed to users, so this is a capacity measure, not a fee one.

Where does your contract sit?

The chain-wide numbers are an average of very different contracts. pev shows exactly which storage slots and methods drive your own contention, and whether a change you ship actually moved it.

See a contract audit →Explore the graph

7-day window · updated 2026-09-09 08:01 UTC · pev indexes from the block it was started, not chain genesis

← back to pev