← previous blocknext block →recent activity
Analyzing
Block #97,728,562
25 transactions · 22 stateful · 2026-08-20 21:17:52 UTC
Parallelism
80/100
Blocked
41%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,728,562 · 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
1w03w06w07w18w09w210w312w113w015w116w117w222w023w424w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5070fb5c…2e6d
0xd32edf…ff58
7 touches
6 conflicts
0x6a9e408e…3721
0x34b655…2a6f
6 touches
3 conflicts
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…001d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002d
0x1b6862…e19c
4 touches
1 conflict
0x8d47c9a4…f11f
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 0x5070fb5ca7…d32e6d
Audit this contract →
← previous block·next block →recent activity