← previous blocknext block →recent activity
Analyzing
Block #86,680,160
24 transactions · 22 stateful · 2026-07-09 18:50:23 UTC
Parallelism
71/100
Blocked
45%
Avg conflicts / tx
0.88
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,680,160 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w06w07w112w214w215w317w120w321w422w523w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x459573ed…fbbe
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x503b3a72…f6df
0x34b655…2a6f
8 touches
6 conflicts
0x3181bd2d…cf15
0xa6afd3…d132
6 touches
3 conflicts
0xf3518e81…757d
0xa6afd3…d132
5 touches
3 conflicts
0x65338476…2209
0x34b655…2a6f
4 touches
1 conflict
0x6daf7ba0…75f7
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
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
10 conflicts on slot 0x459573ed17…94fbbe
Audit this contract →
← previous block·next block →recent activity