← previous blocknext block →recent activity
Analyzing
Block #91,386,235
25 transactions · 17 stateful · 2026-07-29 16:02:01 UTC
Parallelism
80/100
Blocked
47%
Avg conflicts / tx
0.52
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,386,235 · 25 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
1w08w19w010w212w314w015w116w218w319w423w024w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7d7a4a37…f88c
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x9ff176a9…152e
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001e
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002e
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
6 conflicts on slot 0x7d7a4a377a…e3f88c
Audit this contract →
← previous block·next block →recent activity