← previous blocknext block →recent activity
Analyzing
Block #98,028,347
22 transactions · 21 stateful · 2026-08-21 22:40:50 UTC
Parallelism
77/100
Blocked
43%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,028,347 · 22 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
1w02w13w24w06w39w010w111w315w416w018w119w221w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc05f4834…73d1
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x4508f921…7254
0xa6afd3…d132
6 touches
3 conflicts
0x4761ac57…c42c
0xa6afd3…d132
6 touches
3 conflicts
0xd6bd849a…5597
0x2a68ba…90c5
6 touches
3 conflicts
0x9885a25f…2929
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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
6 conflicts on slot 0xc05f4834be…f873d1
Audit this contract →
← previous block·next block →recent activity