← previous blocknext block →recent activity
Analyzing
Block #99,188,562
30 transactions · 27 stateful · 2026-08-26 00:42:02 UTC
Parallelism
80/100
Blocked
56%
Avg conflicts / tx
0.97
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,188,562 · 30 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
1w02w13w24w17w08w29w310w413w314w317w418w525w126w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd69a153d…f309
0xd32edf…ff58
11 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x11258774…9892
0x2a68ba…90c5
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xbb97db90…4c93
0xc8689a…ee79
6 touches
3 conflicts
0x00000000…001a
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002a
0x1b6862…e19c
4 touches
1 conflict
0xd0ec60a1…d242
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 0xd69a153d24…b5f309
Audit this contract →
← previous block·next block →recent activity