← previous blocknext block →recent activity
Analyzing
Block #99,155,461
20 transactions · 18 stateful · 2026-08-25 21:55:30 UTC
Parallelism
70/100
Blocked
67%
Avg conflicts / tx
1.3
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,155,461 · 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
1w02w13w24w35w46w57w310w411w512w013w114w515w219w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x26c5d61f…9c73
0xd32edf…ff58
11 touches
15 conflicts
0xe01158fd…f97e
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…001a
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002a
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
15 conflicts on slot 0x26c5d61f55…879c73
Audit this contract →
← previous block·next block →recent activity