← previous blocknext block →recent activity
Analyzing
Block #99,075,599
66 transactions · 34 stateful · 2026-08-25 15:13:15 UTC
Parallelism
88/100
Blocked
53%
Avg conflicts / tx
0.7
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #99,075,599 · 66 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
1w02w13w24w36w411w547w648w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c3f3122…08e7
0xd32edf…ff58
15 touches
28 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0xe5e7089a…fb91
0x34b655…2a6f
6 touches
3 conflicts
0x11258774…9892
0x2a68ba…90c5
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x91508d45…318b
0x34b655…2a6f
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
28 conflicts on slot 0x1c3f3122fc…5308e7
Audit this contract →
← previous block·next block →recent activity