← previous blocknext block →recent activity
Analyzing
Block #89,839,361
11 transactions · 10 stateful · 2026-07-24 05:57:46 UTC
Parallelism
64/100
Blocked
40%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,839,361 · 11 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w17w08w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe6a9e1dd…41aa
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xd4dfefe7…b85f
0x34b655…2a6f
6 touches
3 conflicts
0x3b8b2dfb…8ffe
0x34b655…2a6f
6 touches
3 conflicts
0xe57232b3…0fbf
0x34b655…2a6f
6 touches
3 conflicts
0x82dd2252…e1ce
0x34b655…2a6f
6 touches
3 conflicts
0xbdc75c16…0d48
0x34b655…2a6f
6 touches
3 conflicts
0x3deaf71f…c229
0x34b655…2a6f
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: Perpl
6 conflicts on slot 0xe6a9e1dd60…ca41aa
Audit this contract →
← previous block·next block →recent activity