← previous blocknext block →recent activity
Analyzing
Block #97,557,732
33 transactions · 23 stateful · 2026-08-20 06:46:25 UTC
Parallelism
85/100
Blocked
43%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,557,732 · 33 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
1w03w15w26w38w014w015w118w019w120w421w122w228w432w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x96c689f6…e7b6
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xcc8faac2…c766
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001a
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002a
0x1b6862…e19c
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 0x96c689f623…bbe7b6
Audit this contract →
← previous block·next block →recent activity