← previous blocknext block →recent activity
Analyzing
Block #99,495,724
20 transactions · 18 stateful · 2026-08-27 02:28:13 UTC
Parallelism
70/100
Blocked
39%
Avg conflicts / tx
0.85
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,495,724 · 20 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
1w02w13w27w011w314w015w416w117w519w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0e1b9848…786d
0xd32edf…ff58
11 touches
15 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x7184c720…ff93
0x34b655…2a6f
4 touches
1 conflict
0x81ca8c9e…28cb
0x34b655…2a6f
4 touches
1 conflict
0x9a100e05…c541
0x34b655…2a6f
4 touches
1 conflict
0xcf70e146…f042
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
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
15 conflicts on slot 0x0e1b984815…78786d
Audit this contract →
← previous block·next block →recent activity