← previous blocknext block →recent activity
Analyzing
Block #97,430,611
13 transactions · 13 stateful · 2026-08-19 20:05:30 UTC
Parallelism
62/100
Blocked
38%
Avg conflicts / tx
0.85
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,430,611 · 13 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
1w02w13w24w36w49w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb69a00d9…4628
0xd32edf…ff58
9 touches
10 conflicts
0x39875c49…67dc
0x34b655…2a6f
4 touches
1 conflict
0x6ccfd182…afae
0x34b655…2a6f
4 touches
1 conflict
0x78eb0de5…1db2
0x01bff4…1071
2 touches
0 conflicts
0x79aeeb89…03e8
0x01bff4…1071
2 touches
0 conflicts
0xbda13e3a…2108
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
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 0xb69a00d933…c94628
Audit this contract →
← previous block·next block →recent activity