← previous blocknext block →recent activity
Analyzing
Block #98,457,294
31 transactions · 27 stateful · 2026-08-23 10:39:51 UTC
Parallelism
71/100
Blocked
59%
Avg conflicts / tx
1.58
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #98,457,294 · 31 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w618w719w825w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x736e494e…1e9e
0xd32edf…ff58
17 touches
36 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
16 touches
28 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…001c
0x1b6862…e19c
16 touches
28 conflicts
0xd996735f…8732
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…002c
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
36 conflicts on slot 0x736e494ed8…d11e9e
Audit this contract →
← previous block·next block →recent activity