← previous blocknext block →recent activity
Analyzing
Block #97,738,919
35 transactions · 29 stateful · 2026-08-20 22:09:59 UTC
Parallelism
77/100
Blocked
62%
Avg conflicts / tx
1.66
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #97,738,919 · 35 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w39w310w411w522w423w524w625w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc26712ed…e9f1
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…0002
0x103de0…bb55
14 touches
21 conflicts
0x00000000…0012
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0013
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…001d
0x1b6862…e19c
12 touches
15 conflicts
0x6b1259e6…4e12
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…002d
0x1b6862…e19c
12 touches
15 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
28 conflicts on slot 0xc26712ed1d…b1e9f1
Audit this contract →
← previous block·next block →recent activity