← previous blocknext block →recent activity
Analyzing
Block #98,739,471
31 transactions · 21 stateful · 2026-08-24 10:55:34 UTC
Parallelism
68/100
Blocked
52%
Avg conflicts / tx
1.29
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #98,739,471 · 31 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
1w02w13w24w35w46w57w610w713w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x336317d8…f1e5
0xd32edf…ff58
17 touches
36 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…0019
0x1b6862…e19c
16 touches
28 conflicts
0x93afca4c…b479
0x1b6862…e19c
16 touches
28 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0029
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 0x336317d818…2df1e5
Audit this contract →
← previous block·next block →recent activity