← previous blocknext block →recent activity
Analyzing
Block #86,103,025
30 transactions · 24 stateful · 2026-07-07 02:32:13 UTC
Parallelism
83/100
Blocked
29%
Avg conflicts / tx
0.47
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,103,025 · 30 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
1w02w13w24w37w28w411w021w023w125w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca02d6fd…66e0
0xd32edf…ff58
9 touches
10 conflicts
0xac33ff75…077b
0xfa32f9…f3f0
6 touches
3 conflicts
0x00000000…0001
0xfa32f9…f3f0
6 touches
3 conflicts
0x00000000…0000
0xfa32f9…f3f0
6 touches
3 conflicts
0x99f666e3…b2a2
0x3bd359…433a
6 touches
3 conflicts
0x9194f4a3…10b8
0x754704…b603
6 touches
3 conflicts
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
0xba5743c7…21c3
0x1b6862…e19c
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 0xca02d6fdc0…8166e0
Audit this contract →
← previous block·next block →recent activity