← previous blocknext block →recent activity
Analyzing
Block #98,552,264
24 transactions · 22 stateful · 2026-08-23 18:47:45 UTC
Parallelism
67/100
Blocked
59%
Avg conflicts / tx
1.58
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #98,552,264 · 24 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w510w114w615w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4fb0558f…86ae
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…002d
0x1b6862…e19c
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x6d43ee99…bdd8
0x1b6862…e19c
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xe89474df…7d73
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0012
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
28 conflicts on slot 0x4fb0558fd1…3386ae
Audit this contract →
← previous block·next block →recent activity