← previous blocknext block →recent activity
Analyzing
Block #99,360,424
36 transactions · 31 stateful · 2026-08-26 15:06:51 UTC
Parallelism
81/100
Blocked
68%
Avg conflicts / tx
1.25
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,360,424 · 36 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
1w02w13w24w36w48w49w010w112w513w616w222w423w531w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4f600f1a…cfd5
0xd32edf…ff58
11 touches
15 conflicts
0x5684aadd…8d62
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 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…001e
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002e
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 0x4f600f1a6d…0ccfd5
Audit this contract →
← previous block·next block →recent activity