← previous blocknext block →recent activity
Analyzing
Block #98,458,510
28 transactions · 22 stateful · 2026-08-23 10:46:00 UTC
Parallelism
64/100
Blocked
64%
Avg conflicts / tx
1.32
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #98,458,510 · 28 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w618w519w722w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3bf0daf…aaa4
0xd32edf…ff58
13 touches
21 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002c
0x1b6862…e19c
8 touches
6 conflicts
0x91220b8f…7a05
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001c
0x1b6862…e19c
8 touches
6 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
21 conflicts on slot 0xf3bf0daf4c…5daaa4
Audit this contract →
← previous block·next block →recent activity