← previous blocknext block →recent activity
Analyzing
Block #97,604,320
25 transactions · 21 stateful · 2026-08-20 10:42:24 UTC
Parallelism
80/100
Blocked
52%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,604,320 · 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
1w02w13w25w07w08w19w010w114w315w416w218w119w320w224w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd5c012ea…6884
0xd32edf…ff58
9 touches
10 conflicts
0x80eee557…711d
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x13985478…9c0e
0x34b655…2a6f
4 touches
1 conflict
0x11258774…9892
0x2a68ba…90c5
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xba19ca5b…f087
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
10 conflicts on slot 0xd5c012eae8…896884
Audit this contract →
← previous block·next block →recent activity