← previous blocknext block →recent activity
Analyzing
Block #98,594,318
24 transactions · 21 stateful · 2026-08-23 22:27:08 UTC
Parallelism
75/100
Blocked
57%
Avg conflicts / tx
1.13
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,594,318 · 24 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
1w02w13w24w37w010w012w313w114w415w517w418w519w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa4e9e47b…f624
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x5c8c6ab6…dc36
0x065c9d…c394
6 touches
3 conflicts
0xffe431af…8faa
0x065c9d…c394
6 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002e
0x1b6862…e19c
4 touches
1 conflict
0xd53220ed…473a
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0012
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
15 conflicts on slot 0xa4e9e47b8e…e3f624
Audit this contract →
← previous block·next block →recent activity