← previous blocknext block →recent activity
Analyzing
Block #86,809,762
12 transactions · 9 stateful · 2026-07-10 09:15:53 UTC
Parallelism
58/100
Blocked
44%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,809,762 · 12 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
3w04w16w210w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x109d8a52…a7b7
0x34b655…2a6f
4 touches
1 conflict
0x16363afe…d410
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6278b1b2…ba7b
0x34b655…2a6f
4 touches
1 conflict
0x683dbabb…acd8
0x34b655…2a6f
4 touches
1 conflict
0x789b9f1f…7bea
0x34b655…2a6f
4 touches
1 conflict
0x7cfe59e0…2ec1
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 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity