← previous blocknext block →recent activity
Analyzing
Block #86,630,161
25 transactions · 19 stateful · 2026-07-09 13:15:10 UTC
Parallelism
76/100
Blocked
47%
Avg conflicts / tx
0.52
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,630,161 · 25 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
1w02w15w06w07w19w210w313w114w417w522w223w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x70ff9262…8d80
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x250c8181…eef2
0x34b655…2a6f
6 touches
3 conflicts
0x5b101190…060e
0x34b655…2a6f
4 touches
1 conflict
0x63c900f4…2600
0x34b655…2a6f
4 touches
1 conflict
0x6e688441…65ee
0x34b655…2a6f
4 touches
1 conflict
0x7ce93f3d…b70e
0x34b655…2a6f
4 touches
1 conflict
0x875c3459…2878
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 0x70ff92623d…f38d80
Audit this contract →
← previous block·next block →recent activity