← previous blocknext block →recent activity
Analyzing
Block #86,694,882
22 transactions · 18 stateful · 2026-07-09 20:28:36 UTC
Parallelism
86/100
Blocked
39%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,694,882 · 22 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w17w08w19w212w013w115w120w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x63c900f4…2600
0x34b655…2a6f
6 touches
3 conflicts
0x7ee6007b…fd68
0x34b655…2a6f
6 touches
3 conflicts
0xbbb9fa77…d121
0x34b655…2a6f
6 touches
3 conflicts
0xe57232b3…0fbf
0x34b655…2a6f
6 touches
3 conflicts
0x922c7ebd…6600
0xc8689a…ee79
6 touches
3 conflicts
0x311f801b…dc74
0x34b655…2a6f
4 touches
1 conflict
0x32c797e4…71c6
0x34b655…2a6f
4 touches
1 conflict
0x3483ab79…8ed3
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
3 conflicts on slot 0x63c900f479…962600
Audit this contract →
← previous block·next block →recent activity