← previous blocknext block →recent activity
Analyzing
Block #91,110,358
23 transactions · 21 stateful · 2026-07-28 16:53:09 UTC
Parallelism
74/100
Blocked
52%
Avg conflicts / tx
1.17
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,110,358 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w07w38w011w112w213w414w116w017w118w319w421w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9119d1fc…8765
0xd32edf…ff58
9 touches
10 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0019
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0029
0x1b6862…e19c
6 touches
3 conflicts
0x0f28fb99…3d2a
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x217bd767…b79e
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x9119d1fcd3…f38765
Audit this contract →
← previous block·next block →recent activity