← previous blocknext block →recent activity
Analyzing
Block #97,529,196
23 transactions · 19 stateful · 2026-08-20 04:22:02 UTC
Parallelism
78/100
Blocked
53%
Avg conflicts / tx
0.78
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,529,196 · 23 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
1w02w13w24w35w08w49w012w413w014w116w118w219w322w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe3c2713d…1d2e
0xd32edf…ff58
9 touches
10 conflicts
0x49cbdb1b…bda4
0x065c9d…c394
6 touches
3 conflicts
0x35c37635…11a6
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0029
0x1b6862…e19c
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x8902ba1f…f4b6
0x34b655…2a6f
4 touches
1 conflict
0x89e2bcda…7267
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
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 0xe3c2713d0a…6c1d2e
Audit this contract →
← previous block·next block →recent activity