← previous blocknext block →recent activity
Analyzing
Block #86,753,225
11 transactions · 7 stateful · 2026-07-10 02:58:24 UTC
Parallelism
73/100
Blocked
29%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,753,225 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3f0e49de…29b6
0x34b655…2a6f
4 touches
1 conflict
0x7d16a9bc…25db
0x34b655…2a6f
4 touches
1 conflict
0x897da50e…1b99
0x34b655…2a6f
4 touches
1 conflict
0xb15f297d…fb80
0x34b655…2a6f
4 touches
1 conflict
0xb15f297d…fb81
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe0a35123…e13e
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
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
1 conflict on slot 0x3f0e49de14…f329b6
Audit this contract →
← previous block·next block →recent activity