← previous blocknext block →recent activity
Analyzing
Block #98,459,427
22 transactions · 19 stateful · 2026-08-23 10:50:38 UTC
Parallelism
68/100
Blocked
47%
Avg conflicts / tx
1.27
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #98,459,427 · 22 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
1w02w13w24w35w49w010w114w515w617w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x31e0f563…f513
0xd32edf…ff58
13 touches
21 conflicts
0x00000000…001c
0x1b6862…e19c
8 touches
6 conflicts
0x544745e8…d72e
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…002c
0x1b6862…e19c
8 touches
6 conflicts
0xd0ec60a1…d244
0x1b6862…e19c
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
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
21 conflicts on slot 0x31e0f56382…92f513
Audit this contract →
← previous block·next block →recent activity