← previous blocknext block →recent activity
Analyzing
Block #99,038,770
30 transactions · 28 stateful · 2026-08-25 12:04:47 UTC
Parallelism
67/100
Blocked
54%
Avg conflicts / tx
1.5
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #99,038,770 · 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
1w02w13w24w35w46w57w69w211w118w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xddc60686…8c12
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…002f
0x1b6862…e19c
10 touches
10 conflicts
0x93afca4c…b47f
0x1b6862…e19c
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 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
28 conflicts on slot 0xddc60686b8…1d8c12
Audit this contract →
← previous block·next block →recent activity