← previous blocknext block →recent activity
Analyzing
Block #86,104,360
22 transactions · 19 stateful · 2026-07-07 02:41:07 UTC
Parallelism
77/100
Blocked
37%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,104,360 · 22 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
1w02w13w05w16w07w18w29w313w014w118w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbfc6f2…041d
0xd32edf…ff58
9 touches
10 conflicts
0xe5eb3c33…0e3a
0x34b655…2a6f
4 touches
1 conflict
0xacd1b162…bee6
0x34b655…2a6f
4 touches
1 conflict
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0xdd70bea3…1ffe
0x3bd359…433a
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0x2b9c6652…d14e
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
10 conflicts on slot 0xbcbfc6f26a…fb041d
Audit this contract →
← previous block·next block →recent activity