← previous blocknext block →recent activity
Analyzing
Block #86,659,629
18 transactions · 9 stateful · 2026-07-09 16:33:22 UTC
Parallelism
78/100
Blocked
33%
Avg conflicts / tx
0.22
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,659,629 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xef7cdebf…b33b
0x34b655…2a6f
6 touches
3 conflicts
0x17fff7d7…7b99
0x34b655…2a6f
4 touches
1 conflict
0x17fff7d7…7b9a
0x34b655…2a6f
4 touches
1 conflict
0x309e57d5…2008
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x521553ff…d548
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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 0xef7cdebfc1…cab33b
Audit this contract →
← previous block·next block →recent activity