← previous blocknext block →recent activity
Analyzing
Block #98,766,365
30 transactions · 21 stateful · 2026-08-24 13:11:00 UTC
Parallelism
70/100
Blocked
57%
Avg conflicts / tx
1.37
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #98,766,365 · 30 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
1w02w13w24w35w46w515w619w721w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc4f25d67…9269
0xd32edf…ff58
17 touches
36 conflicts
0x00000000…002a
0x1b6862…e19c
6 touches
3 conflicts
0x5c8c6ab6…dc36
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001a
0x1b6862…e19c
6 touches
3 conflicts
0x1045386d…cb88
0x1b6862…e19c
6 touches
3 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 0xc4f25d6711…169269
Audit this contract →
← previous block·next block →recent activity