← previous blocknext block →recent activity
Analyzing
Block #86,632,343
11 transactions · 11 stateful · 2026-07-09 13:29:48 UTC
Parallelism
64/100
Blocked
27%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,632,343 · 11 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8eb0ac6b…a73a
0x34b655…2a6f
6 touches
3 conflicts
0x9365e097…ff56
0x34b655…2a6f
6 touches
3 conflicts
0x2e30c36b…b1fa
0x34b655…2a6f
4 touches
1 conflict
0x304f46e4…3f46
0x34b655…2a6f
4 touches
1 conflict
0x32409e80…a396
0x34b655…2a6f
4 touches
1 conflict
0x3d248e74…b607
0x34b655…2a6f
4 touches
1 conflict
0x3ee77819…1b54
0x34b655…2a6f
4 touches
1 conflict
0x3fa1fac4…826c
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 0x8eb0ac6bf2…4da73a
Audit this contract →
← previous block·next block →recent activity