← previous blocknext block →recent activity
Analyzing
Block #91,097,539
18 transactions · 15 stateful · 2026-07-28 15:48:39 UTC
Parallelism
72/100
Blocked
67%
Avg conflicts / tx
1.11
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,097,539 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w25w16w28w010w311w112w214w415w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x601d2a88…b330
0xd32edf…ff58
9 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x9adb2803…81f1
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0018
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0028
0x1b6862…e19c
4 touches
1 conflict
0xb538c6fa…9ae5
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
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
10 conflicts on slot 0x601d2a8886…dcb330
Audit this contract →
← previous block·next block →recent activity