← previous blocknext block →recent activity
Analyzing
Block #98,505,226
64 transactions · 51 stateful · 2026-08-23 14:42:21 UTC
Parallelism
67/100
Blocked
63%
Avg conflicts / tx
3.73
Longest chain
21 deep
Execution timeline
did this block parallelize well?
view
block #98,505,226 · 64 txs across 21 waves · depth 21
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
wave w19
wave w20
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w26w37w48w59w610w712w813w914w1015w1116w1218w1333w1434w1535w1636w1737w1843w19
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8ebd9627…f6f6
0xd32edf…ff58
39 touches
190 conflicts
0x00000000…0012
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0013
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0015
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…001d
0x1b6862…e19c
16 touches
28 conflicts
0xd0ec60a1…d245
0x1b6862…e19c
16 touches
28 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…002d
0x1b6862…e19c
16 touches
28 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
190 conflicts on slot 0x8ebd96271b…29f6f6
Audit this contract →
← previous block·next block →recent activity