← previous blocknext block →recent activity
Analyzing
Block #86,691,477
14 transactions · 13 stateful · 2026-07-09 20:05:54 UTC
Parallelism
79/100
Blocked
23%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,691,477 · 14 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
5w06w07w18w212w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc06b563…c7fc
0x34b655…2a6f
6 touches
3 conflicts
0x3ba014e3…35d5
0x34b655…2a6f
4 touches
1 conflict
0x9fd372a1…a959
0x34b655…2a6f
4 touches
1 conflict
0x64f6100d…92bd
0x34b655…2a6f
4 touches
1 conflict
0xbdc80bf7…e947
0x34b655…2a6f
4 touches
1 conflict
0xd192f4ed…d7ec
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x6ca0994e…02ef
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 0xcc06b56342…84c7fc
Audit this contract →
← previous block·next block →recent activity