← previous blocknext block →recent activity
Analyzing
Block #86,082,162
25 transactions · 21 stateful · 2026-07-07 00:12:59 UTC
Parallelism
68/100
Blocked
48%
Avg conflicts / tx
1.24
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,082,162 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w59w111w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x63f02df9…6ce8
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
0x44d7acbf…e67e
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xd9f1e40f…09a3
0x3bd359…433a
4 touches
1 conflict
0x504ac60b…20a6
0x754704…b603
4 touches
1 conflict
0x527f20e3…82e7
0x754704…b603
4 touches
1 conflict
0xa1087a5c…66c4
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
28 conflicts on slot 0x63f02df95a…dd6ce8
Audit this contract →
← previous block·next block →recent activity