← previous blocknext block →recent activity
Analyzing
Block #86,271,004
23 transactions · 20 stateful · 2026-07-07 21:13:46 UTC
Parallelism
70/100
Blocked
50%
Avg conflicts / tx
1.13
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,271,004 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w410w216w619w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf877a2f3…ca38
0xd32edf…ff58
13 touches
21 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xd154c754…dab4
0x065c9d…c394
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0018
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0028
0x1b6862…e19c
4 touches
1 conflict
0xd996735f…872e
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
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
21 conflicts on slot 0xf877a2f3ae…86ca38
Audit this contract →
← previous block·next block →recent activity