← previous blocknext block →recent activity
Analyzing
Block #97,522,244
24 transactions · 21 stateful · 2026-08-20 03:47:04 UTC
Parallelism
88/100
Blocked
33%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,522,244 · 24 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
1w03w15w06w09w010w011w113w214w017w120w021w122w123w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x62bf268f…b80c
0xd32edf…ff58
5 touches
3 conflicts
0x91220b8f…7a02
0x1b6862…e19c
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x01e7b865…6e6d
0x188d58…ea8e
4 touches
1 conflict
0x00000000…0012
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
3 conflicts on slot 0x62bf268ff6…99b80c
Audit this contract →
← previous block·next block →recent activity