← previous blocknext block →recent activity
Analyzing
Block #89,848,227
35 transactions · 29 stateful · 2026-07-24 06:42:27 UTC
Parallelism
80/100
Blocked
52%
Avg conflicts / tx
1.23
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #89,848,227 · 35 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
2w04w05w06w19w110w011w112w013w116w217w318w419w524w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe3507347…b218
0xd32edf…ff58
13 touches
21 conflicts
0xe9b8c144…e5be
0x3bd359…433a
10 touches
10 conflicts
0x6af306bb…2e81
0x3bd359…433a
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001f
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002f
0x1b6862…e19c
8 touches
6 conflicts
0x93afca4c…b47f
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
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 0xe350734761…3eb218
Audit this contract →
← previous block·next block →recent activity