← previous blocknext block →recent activity
Analyzing
Block #86,916,182
14 transactions · 11 stateful · 2026-07-10 21:07:34 UTC
Parallelism
79/100
Blocked
36%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,916,182 · 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
1w02w03w14w05w18w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xed660153…a905
0x34b655…2a6f
6 touches
3 conflicts
0x076fa926…c409
0x34b655…2a6f
4 touches
1 conflict
0x157dbfb2…4089
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x23876918…de57
0x34b655…2a6f
4 touches
1 conflict
0x26b3b71d…93c1
0x34b655…2a6f
4 touches
1 conflict
0x3ccc3d17…de83
0x34b655…2a6f
4 touches
1 conflict
0x3d91ef7c…72df
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 0xed66015380…82a905
Audit this contract →
← previous block·next block →recent activity