← previous blocknext block →recent activity
Analyzing
Block #99,163,938
17 transactions · 15 stateful · 2026-08-25 22:38:09 UTC
Parallelism
65/100
Blocked
53%
Avg conflicts / tx
0.71
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,163,938 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w17w08w011w412w114w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x30731027…f728
0xd32edf…ff58
7 touches
6 conflicts
0xa5a4bb2c…f2c7
0x0eb88f…c0cc
4 touches
1 conflict
0x388d69c4…4288
0x188d58…ea8e
4 touches
1 conflict
0xa5a4bb2c…f2c7
0x188d58…ea8e
4 touches
1 conflict
0xd9a7cef1…1ed5
0x188d58…ea8e
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
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
6 conflicts on slot 0x3073102725…d8f728
Audit this contract →
← previous block·next block →recent activity