← previous blocknext block →recent activity
Analyzing
Block #98,642,331
30 transactions · 20 stateful · 2026-08-24 02:37:01 UTC
Parallelism
80/100
Blocked
40%
Avg conflicts / tx
0.5
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,642,331 · 30 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
1w06w18w29w010w111w318w219w423w324w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x07647418…e4e4
0xd32edf…ff58
7 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x831e08aa…eb97
0x065c9d…c394
5 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x206f4379…e08a
0x34b655…2a6f
4 touches
1 conflict
0xcb45d9d6…cb87
0x1b6862…e19c
4 touches
1 conflict
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
6 conflicts on slot 0x0764741865…11e4e4
Audit this contract →
← previous block·next block →recent activity