← previous blocknext block →recent activity
Analyzing
Block #99,212,340
40 transactions · 36 stateful · 2026-08-26 02:41:39 UTC
Parallelism
80/100
Blocked
44%
Avg conflicts / tx
1.15
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #99,212,340 · 40 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w310w411w517w418w519w623w625w728w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfead9cb8…d786
0xd32edf…ff58
13 touches
21 conflicts
0x889d5e90…929a
0x2a68ba…90c5
12 touches
15 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
0x6b1259e6…4e10
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
21 conflicts on slot 0xfead9cb85e…0cd786
Audit this contract →
← previous block·next block →recent activity