← previous blocknext block →recent activity
Analyzing
Block #99,504,559
23 transactions · 18 stateful · 2026-08-27 03:12:41 UTC
Parallelism
83/100
Blocked
56%
Avg conflicts / tx
0.65
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,504,559 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w08w19w111w212w213w314w215w016w017w119w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x69df994a…4065
0xd32edf…ff58
7 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x3a921be0…779c
0x2a68ba…90c5
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x6dbeaded…8e64
0x40c49f…2af0
4 touches
1 conflict
0xd4c0b9e2…ed1e
0x40c49f…2af0
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 0x69df994a35…4e4065
Audit this contract →
← previous block·next block →recent activity