← previous blocknext block →recent activity
Analyzing
Block #85,987,095
26 transactions · 21 stateful · 2026-07-06 13:38:20 UTC
Parallelism
88/100
Blocked
29%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,987,095 · 26 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
1w04w05w06w07w18w19w114w115w221w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x822f8512…68e0
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…7212
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0xa014d511…0dbf
0xd32edf…ff58
3 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…001a
0x1b6862…e19c
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 0x822f8512e8…4668e0
Audit this contract →
← previous block·next block →recent activity