← previous blocknext block →recent activity
Analyzing
Block #86,733,158
23 transactions · 21 stateful · 2026-07-10 00:44:14 UTC
Parallelism
78/100
Blocked
62%
Avg conflicts / tx
1.04
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,733,158 · 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
1w02w13w24w35w18w19w010w113w114w415w216w317w319w220w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1a063907…d518
0xd32edf…ff58
9 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x1321736a…43e3
0x34b655…2a6f
4 touches
1 conflict
0x17c3727d…cb0e
0x34b655…2a6f
4 touches
1 conflict
0x1c03f81f…b303
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 0x1a063907bd…9fd518
Audit this contract →
← previous block·next block →recent activity