← previous blocknext block →recent activity
Analyzing
Block #86,231,565
35 transactions · 23 stateful · 2026-07-07 16:50:26 UTC
Parallelism
89/100
Blocked
39%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,231,565 · 35 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w06w17w08w19w214w115w216w017w118w219w023w328w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x289295fe…37f0
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0002
0x04fdea…47d7
6 touches
3 conflicts
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0xcda18b0b…6a4c
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xac4a2e96…1d5c
0x065c9d…c394
3 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
6 conflicts on slot 0x289295fe43…f337f0
Audit this contract →
← previous block·next block →recent activity