← previous blocknext block →recent activity
Analyzing
Block #86,233,319
29 transactions · 23 stateful · 2026-07-07 17:02:09 UTC
Parallelism
79/100
Blocked
39%
Avg conflicts / tx
0.72
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,233,319 · 29 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w27w08w19w210w311w412w514w423w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3c584d66…1d3c
0xd32edf…ff58
11 touches
15 conflicts
0xdfa159d0…1576
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xcc4f1f14…aa5f
0x065c9d…c394
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x12309510…0ac2
0x000000…012a
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x1c354dc0…96de
0x754704…b603
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: FastLane: FastLaneAuctionHandler
15 conflicts on slot 0x3c584d663f…931d3c
Audit this contract →
← previous block·next block →recent activity