← previous blocknext block →recent activity
Analyzing
Block #97,558,286
25 transactions · 20 stateful · 2026-08-20 06:49:13 UTC
Parallelism
88/100
Blocked
45%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,558,286 · 25 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
1w02w13w24w05w06w07w18w19w116w117w119w124w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1946cd1e…6a65
0xd32edf…ff58
5 touches
3 conflicts
0x01e7b865…6e6d
0x188d58…ea8e
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…001a
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002a
0x1b6862…e19c
4 touches
1 conflict
0x3e04662b…0da3
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 0x1946cd1e7d…4d6a65
Audit this contract →
← previous block·next block →recent activity