← previous blocknext block →recent activity
Analyzing
Block #98,498,991
20 transactions · 19 stateful · 2026-08-23 14:09:53 UTC
Parallelism
70/100
Blocked
47%
Avg conflicts / tx
1.1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,498,991 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w310w411w512w013w415w116w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdc1c5d1a…658c
0xd32edf…ff58
11 touches
15 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001c
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002c
0x1b6862…e19c
8 touches
6 conflicts
0xc13fac9b…d2d2
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
15 conflicts on slot 0xdc1c5d1a86…72658c
Audit this contract →
← previous block·next block →recent activity