← previous blocknext block →recent activity
Analyzing
Block #99,080,387
30 transactions · 26 stateful · 2026-08-25 15:37:31 UTC
Parallelism
67/100
Blocked
62%
Avg conflicts / tx
1.27
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #99,080,387 · 30 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w610w711w818w524w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc246ca3…78ef
0xd32edf…ff58
11 touches
15 conflicts
0x41755291…977f
0x065c9d…c394
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0018
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0028
0x1b6862…e19c
8 touches
6 conflicts
0x9885a25f…2926
0x1b6862…e19c
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
15 conflicts on slot 0xcc246ca37f…2b78ef
Audit this contract →
← previous block·next block →recent activity