← previous blocknext block →recent activity
Analyzing
Block #97,431,485
18 transactions · 16 stateful · 2026-08-19 20:09:53 UTC
Parallelism
72/100
Blocked
44%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,431,485 · 18 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
1w02w13w26w37w012w013w114w315w416w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0800eb55…d54c
0xd32edf…ff58
5 touches
3 conflicts
0x11b69a7e…334e
0x01bff4…1071
4 touches
1 conflict
0x00000000…003d
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…001f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002f
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
3 conflicts on slot 0x0800eb5537…3ed54c
Audit this contract →
← previous block·next block →recent activity