← previous blocknext block →recent activity
Analyzing
Block #86,946,257
23 transactions · 20 stateful · 2026-07-11 00:28:30 UTC
Parallelism
78/100
Blocked
40%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,946,257 · 23 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
1w02w13w24w35w410w011w112w220w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe2d33de7…4ff6
0xd32edf…ff58
9 touches
10 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x3ee77819…1b54
0x34b655…2a6f
4 touches
1 conflict
0x446833f1…7196
0x34b655…2a6f
4 touches
1 conflict
0x4e8f6282…a7eb
0x34b655…2a6f
4 touches
1 conflict
0x727fbce7…0c80
0x34b655…2a6f
4 touches
1 conflict
0x751856da…cf07
0x34b655…2a6f
4 touches
1 conflict
0x7523ad90…2ba5
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: FastLane: FastLaneAuctionHandler
10 conflicts on slot 0xe2d33de7f3…494ff6
Audit this contract →
← previous block·next block →recent activity