← previous blocknext block →recent activity
Analyzing
Block #97,730,368
29 transactions · 19 stateful · 2026-08-20 21:26:58 UTC
Parallelism
79/100
Blocked
47%
Avg conflicts / tx
0.66
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,730,368 · 29 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w016w418w519w020w121w322w428w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5f524ae7…4238
0xd32edf…ff58
11 touches
15 conflicts
0xe483d4e3…e530
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002d
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 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
15 conflicts on slot 0x5f524ae7e4…444238
Audit this contract →
← previous block·next block →recent activity