← previous blocknext block →recent activity
Analyzing
Block #99,617,934
25 transactions · 20 stateful · 2026-08-27 12:49:43 UTC
Parallelism
68/100
Blocked
60%
Avg conflicts / tx
1.56
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #99,617,934 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w48w515w616w721w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9b10647c…3c1d
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x9ac040c1…8222
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x11258774…9892
0x2a68ba…90c5
8 touches
6 conflicts
0x72d21b75…5927
0x065c9d…c394
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
28 conflicts on slot 0x9b10647c1c…c33c1d
Audit this contract →
← previous block·next block →recent activity