← previous blocknext block →recent activity
Analyzing
Block #91,447,251
21 transactions · 21 stateful · 2026-07-29 21:10:14 UTC
Parallelism
81/100
Blocked
52%
Avg conflicts / tx
0.9
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,447,251 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w07w08w19w210w011w112w214w015w116w118w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x88ae8825…eaeb
0xd32edf…ff58
7 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0x48cba2…b48b
6 touches
3 conflicts
0x424934c8…f2f1
0x34b655…2a6f
4 touches
1 conflict
0x28f324ed…9db7
0x34b655…2a6f
4 touches
1 conflict
0x2d6fda24…c638
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0xa38c430a…e3cb
0x34b655…2a6f
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
6 conflicts on slot 0x88ae88255d…d1eaeb
Audit this contract →
← previous block·next block →recent activity