← previous blocknext block →recent activity
Analyzing
Block #86,611,833
22 transactions · 18 stateful · 2026-07-09 11:12:48 UTC
Parallelism
77/100
Blocked
39%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,611,833 · 22 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
1w02w03w16w07w111w217w118w219w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x93459a00…1fc2
0x34b655…2a6f
6 touches
3 conflicts
0x94ba9c4a…41d8
0x34b655…2a6f
6 touches
3 conflicts
0x5f251b96…6054
0x34b655…2a6f
6 touches
3 conflicts
0x3347cbe5…846c
0x34b655…2a6f
6 touches
3 conflicts
0x3bdab090…c5bf
0x34b655…2a6f
6 touches
3 conflicts
0x97b0b2ee…4666
0x34b655…2a6f
4 touches
1 conflict
0xc166a323…1f33
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity