← previous blocknext block →recent activity
Analyzing
Block #97,386,264
30 transactions · 23 stateful · 2026-08-19 16:07:32 UTC
Parallelism
80/100
Blocked
43%
Avg conflicts / tx
0.7
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,386,264 · 30 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
1w02w13w24w35w410w111w512w014w120w021w122w224w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3a096d6f…791d
0xd32edf…ff58
9 touches
10 conflicts
0x97f44a2e…c907
0x065c9d…c394
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…001e
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002e
0x1b6862…e19c
6 touches
3 conflicts
0x511f46a7…edae
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
10 conflicts on slot 0x3a096d6fc0…d0791d
Audit this contract →
← previous block·next block →recent activity