← previous blocknext block →recent activity
Analyzing
Block #99,249,532
24 transactions · 19 stateful · 2026-08-26 05:48:47 UTC
Parallelism
71/100
Blocked
47%
Avg conflicts / tx
0.71
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,249,532 · 24 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
1w02w13w24w15w37w08w49w510w616w623w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x533f96c5…d1b4
0xd32edf…ff58
9 touches
10 conflicts
0x2ce2d49e…d188
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001b
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002b
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
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
10 conflicts on slot 0x533f96c5e2…2ad1b4
Audit this contract →
← previous block·next block →recent activity