← previous blocknext block →recent activity
Analyzing
Block #86,904,323
18 transactions · 11 stateful · 2026-07-10 19:48:19 UTC
Parallelism
78/100
Blocked
27%
Avg conflicts / tx
0.28
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,904,323 · 18 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
3w06w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9138a113…0d5f
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0xe954af0e…b8f3
0x34b655…2a6f
4 touches
1 conflict
0x1f9a46d9…c90b
0x34b655…2a6f
4 touches
1 conflict
0x58627b98…92ad
0x34b655…2a6f
4 touches
1 conflict
0x58627b98…92ae
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 0x9138a113b1…c30d5f
Audit this contract →
← previous block·next block →recent activity