← previous blocknext block →recent activity
Analyzing
Block #98,838,039
28 transactions · 24 stateful · 2026-08-24 19:11:49 UTC
Parallelism
64/100
Blocked
63%
Avg conflicts / tx
1.54
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #98,838,039 · 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
1w02w13w24w35w411w513w116w718w819w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0163d02e…ae18
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001b
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002b
0x1b6862…e19c
8 touches
6 conflicts
0x1da7723c…80aa
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
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
28 conflicts on slot 0x0163d02ed4…c3ae18
Audit this contract →
← previous block·next block →recent activity