← previous blocknext block →recent activity
Analyzing
Block #98,206,365
31 transactions · 22 stateful · 2026-08-22 13:37:15 UTC
Parallelism
77/100
Blocked
59%
Avg conflicts / tx
0.9
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #98,206,365 · 31 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w07w39w410w512w618w420w523w430w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51b5dfb5…8e1f
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…0002
0xbb3f3c…e046
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001f
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002f
0x1b6862…e19c
6 touches
3 conflicts
0xd996735f…8735
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
15 conflicts on slot 0x51b5dfb5b1…218e1f
Audit this contract →
← previous block·next block →recent activity