← previous blocknext block →recent activity
Analyzing
Block #99,209,096
70 transactions · 50 stateful · 2026-08-26 02:25:20 UTC
Parallelism
67/100
Blocked
76%
Avg conflicts / tx
3.4
Longest chain
23 deep
Execution timeline
did this block parallelize well?
view
block #99,209,096 · 70 txs across 23 waves · depth 23
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
wave w19
wave w20
wave w21
wave w22
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w810w911w1012w1135w1243w1345w1547w1759w18
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x12958005…802c
0xd32edf…ff58
33 touches
136 conflicts
0x00000000…0013
0x1b6862…e19c
24 touches
66 conflicts
0x00000000…0015
0x1b6862…e19c
24 touches
66 conflicts
0x00000000…001b
0x1b6862…e19c
24 touches
66 conflicts
0x00000000…002b
0x1b6862…e19c
24 touches
66 conflicts
0xd5b10148…e634
0x1b6862…e19c
24 touches
66 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
24 touches
66 conflicts
0x00000000…0012
0x1b6862…e19c
24 touches
66 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
136 conflicts on slot 0x1295800504…b2802c
Audit this contract →
← previous block·next block →recent activity