← previous blocknext block →recent activity
Analyzing
Block #99,484,929
20 transactions · 17 stateful · 2026-08-27 01:33:52 UTC
Parallelism
70/100
Blocked
53%
Avg conflicts / tx
1.1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,484,929 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w09w410w411w512w013w115w116w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b939905…974e
0xd32edf…ff58
11 touches
15 conflicts
0x046a928e…0012
0x2a68ba…90c5
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x306cc7da…f06f
0x065c9d…c394
6 touches
3 conflicts
0xba5743c7…21bf
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x51af0e92…4020
0x34b655…2a6f
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
15 conflicts on slot 0x2b93990509…d3974e
Audit this contract →
← previous block·next block →recent activity