← previous blocknext block →recent activity
Analyzing
Block #86,737,145
20 transactions · 17 stateful · 2026-07-10 01:10:51 UTC
Parallelism
80/100
Blocked
53%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,737,145 · 20 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
1w02w13w25w27w08w19w010w113w314w015w116w217w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x939df7a3…314e
0xd32edf…ff58
5 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x2d1d07e4…eeda
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x427f51fd…bd80
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x49eb4894…b9d1
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
3 conflicts on slot 0x939df7a3ef…c3314e
Audit this contract →
← previous block·next block →recent activity