← previous blocknext block →recent activity
Analyzing
Block #86,289,225
30 transactions · 24 stateful · 2026-07-07 23:15:22 UTC
Parallelism
73/100
Blocked
54%
Avg conflicts / tx
1.1
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,289,225 · 30 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
1w02w14w25w36w07w28w015w416w517w618w120w321w123w729w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x67eec428…eb6e
0xd32edf…ff58
13 touches
21 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x8cd684d0…c3cb
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0018
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0028
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 0x67eec428e3…f1eb6e
Audit this contract →
← previous block·next block →recent activity