← previous blocknext block →recent activity
Analyzing
Block #90,625,221
20 transactions · 17 stateful · 2026-07-27 00:11:30 UTC
Parallelism
75/100
Blocked
41%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,625,221 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w27w08w19w210w311w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6237f1a7…2f59
0x3bd359…433a
8 touches
6 conflicts
0x66312019…f62e
0xe7cd86…c82d
8 touches
6 conflicts
0x00000000…0004
0x47bae1…7568
8 touches
6 conflicts
0x00000000…0000
0x47bae1…7568
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0003
0x47bae1…7568
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x63d273cc…f2ec
0x80f006…d585
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Wrapped MON (WMON)
6 conflicts on slot 0x6237f1a72f…332f59
Audit this contract →
← previous block·next block →recent activity