← previous blocknext block →recent activity
Analyzing
Block #86,661,374
18 transactions · 17 stateful · 2026-07-09 16:45:01 UTC
Parallelism
72/100
Blocked
24%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,661,374 · 18 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
2w07w18w211w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7a693a45…747c
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xe5a9274d…78d7
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x3fa1fac4…826c
0x34b655…2a6f
4 touches
1 conflict
0x41b014d9…6c12
0x34b655…2a6f
4 touches
1 conflict
0x41b014d9…6c13
0x34b655…2a6f
4 touches
1 conflict
0x486c1db0…955c
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 0x7a693a4513…8e747c
Audit this contract →
← previous block·next block →recent activity