← previous blocknext block →recent activity
Analyzing
Block #91,248,254
21 transactions · 20 stateful · 2026-07-29 04:26:51 UTC
Parallelism
86/100
Blocked
20%
Avg conflicts / tx
0.24
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,248,254 · 21 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w010w011w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x67f6f519…8e1c
0xd32edf…ff58
5 touches
3 conflicts
0x1e81ea5f…2510
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xa523c16d…15cd
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x342fbbca…d443
0x40c49f…2af0
4 touches
1 conflict
0x8f478f26…9d56
0x000000…012a
2 touches
0 conflicts
0x984bf48e…65c7
0x000000…012a
2 touches
0 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
3 conflicts on slot 0x67f6f519ba…838e1c
Audit this contract →
← previous block·next block →recent activity