← previous blocknext block →recent activity
Analyzing
Block #86,678,309
20 transactions · 13 stateful · 2026-07-09 18:38:00 UTC
Parallelism
85/100
Blocked
15%
Avg conflicts / tx
0.15
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,678,309 · 20 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
6w07w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x56b5f5c0…a3ad
0x34b655…2a6f
6 touches
3 conflicts
0xc5decd02…dbf4
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x79287e09…898a
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
2 touches
0 conflicts
0x6f232437…749d
0x34b655…2a6f
2 touches
0 conflicts
0x9210e826…1414
0x34b655…2a6f
2 touches
0 conflicts
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 0x56b5f5c03e…07a3ad
Audit this contract →
← previous block·next block →recent activity