← previous blocknext block →recent activity
Analyzing
Block #86,697,841
18 transactions · 16 stateful · 2026-07-09 20:48:20 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.94
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,697,841 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w17w29w310w411w516w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x4b2b1640…1bb8
0x34b655…2a6f
6 touches
3 conflicts
0x017975b8…fd4c
0x34b655…2a6f
6 touches
3 conflicts
0x6f900be0…cd6e
0x34b655…2a6f
4 touches
1 conflict
0x75854a6e…5d6d
0x34b655…2a6f
4 touches
1 conflict
0x75854a6e…5d6e
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
15 conflicts on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity