← previous blocknext block →recent activity
Analyzing
Block #91,958,709
24 transactions · 23 stateful · 2026-07-31 16:03:15 UTC
Parallelism
63/100
Blocked
52%
Avg conflicts / tx
1.38
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #91,958,709 · 24 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w37w410w511w613w716w119w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xebfea288…84b8
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…001a
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002a
0x1b6862…e19c
8 touches
6 conflicts
0x91220b8f…7a03
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
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
28 conflicts on slot 0xebfea28855…5884b8
Audit this contract →
← previous block·next block →recent activity