← previous blocknext block →recent activity
Analyzing
Block #86,692,403
13 transactions · 9 stateful · 2026-07-09 20:12:03 UTC
Parallelism
62/100
Blocked
56%
Avg conflicts / tx
0.85
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,692,403 · 13 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
2w05w06w17w28w19w310w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x12bc23cf…d56d
0x34b655…2a6f
4 touches
1 conflict
0x42523a73…c021
0x34b655…2a6f
4 touches
1 conflict
0x5f0db4a6…1874
0x34b655…2a6f
4 touches
1 conflict
0x5f0db4a6…1875
0x34b655…2a6f
4 touches
1 conflict
0x6d11d4a8…3a2d
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity