← previous blocknext block →recent activity
Analyzing
Block #99,112,600
21 transactions · 20 stateful · 2026-08-25 18:19:46 UTC
Parallelism
67/100
Blocked
60%
Avg conflicts / tx
1.29
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,112,600 · 21 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
1w02w13w24w05w26w37w08w112w413w514w615w217w419w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd394992a…f101
0xd32edf…ff58
11 touches
15 conflicts
0x11258774…9892
0x2a68ba…90c5
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
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…0019
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0029
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 0xd394992a4f…89f101
Audit this contract →
← previous block·next block →recent activity