← previous blocknext block →recent activity
Analyzing
Block #98,772,259
30 transactions · 23 stateful · 2026-08-24 13:40:39 UTC
Parallelism
83/100
Blocked
39%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,772,259 · 30 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w08w111w014w015w118w219w120w221w024w326w127w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5ea0ea30…d23b
0xd32edf…ff58
7 touches
6 conflicts
0x41755291…977f
0x065c9d…c394
6 touches
3 conflicts
0x5784baac…ac7e
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x5d82c9b5…004c
0x3bd359…433a
4 touches
1 conflict
0xcce2fd99…a8eb
0x3bd359…433a
4 touches
1 conflict
0x00000000…0003
0x5afd3e…7620
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 0x5ea0ea3008…96d23b
Audit this contract →
← previous block·next block →recent activity