← previous blocknext block →recent activity
Analyzing
Block #86,692,056
21 transactions · 15 stateful · 2026-07-09 20:09:44 UTC
Parallelism
71/100
Blocked
53%
Avg conflicts / tx
0.52
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,692,056 · 21 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
1w02w16w07w19w210w211w313w414w120w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9199a85a…acd9
0x34b655…2a6f
6 touches
3 conflicts
0xc5decd02…dbf4
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x392726fc…489e
0x34b655…2a6f
4 touches
1 conflict
0x392726fc…489f
0x34b655…2a6f
4 touches
1 conflict
0x3d4c0233…20a5
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x521dfc1d…edbb
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 0x9199a85ae5…d3acd9
Audit this contract →
← previous block·next block →recent activity