pev.How Monad parallelizes
Analytics · last 7 days
How Monad parallelizes.
Real numbers from 1,224,932 blocks indexed over the last 7 days. The chart is the chain’s parallelism score, day by day. The list below is who caused the contention.
Avg parallelism
81.2/100
Blocks
1,224,932
Transactions
10,592,882
Conflicts
2,207,964
Daily parallelism
70+ clean40-69 contended< 40 throughput-killer
Conflict kinds
What kind of contention dominates the chain.
WRITE / WRITE94%1,585,391
both txs wrote the same slot
MIXED5%91,629
the same pair conflicted on slots in multiple ways
READ / WRITE1%16,503
one tx read a slot the other wrote
Wave depth
How many sequential rounds blocks needed. 65% ran fully parallel.
1 wave65%797,219
2 waves23%282,835
3 waves6%71,933
4+ waves6%72,947
1,224,934 blocks total
Top conflict-causing contracts
Ranked by total conflicts caused over the window. Click any row to inspect the contract’s parallelism profile.
Top contended storage slots· last 24h
One level deeper than the contract list, the exact (contract, slot) pairs causing the most contention. Click to inspect the contract.
Top conflict-causing methods· last 24h
The function selectors causing the most outbound conflicts, summed across every contract that calls them. Resolved against 4byte when known.
Stats above are aggregated over blocks #71,092,445 to #72,317,445, roughly the last 7 days of mainnet at current cadence. Conflict counts are absolute (no rate normalization), so contracts with more total transactions naturally appear higher on the list. Names are shown when verified on Sourcify (rare on Monad mainnet right now); otherwise we show the short hex.