← previous blocknext block →recent activity
Analyzing
Block #91,417,310
18 transactions · 17 stateful · 2026-07-29 18:38:44 UTC
Parallelism
67/100
Blocked
59%
Avg conflicts / tx
1.28
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,417,310 · 18 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
1w02w14w25w36w47w08w19w210w311w515w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc4b3eada…664b
0xd32edf…ff58
11 touches
15 conflicts
0xf9e23360…8ef7
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0x0f94ee4c…189e
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
15 conflicts on slot 0xc4b3eada3b…0c664b
Audit this contract →
← previous block·next block →recent activity