← previous blocknext block →recent activity
Analyzing
Block #99,160,768
35 transactions · 29 stateful · 2026-08-25 22:22:12 UTC
Parallelism
80/100
Blocked
66%
Avg conflicts / tx
1.4
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,160,768 · 35 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w08w29w311w420w521w224w626w432w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5160e9e…dd22
0xd32edf…ff58
13 touches
21 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001a
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002a
0x1b6862…e19c
6 touches
3 conflicts
0x69017fce…85bd
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
21 conflicts on slot 0xf5160e9e55…99dd22
Audit this contract →
← previous block·next block →recent activity