← previous blocknext block →recent activity
Analyzing
Block #99,192,136
25 transactions · 19 stateful · 2026-08-26 01:00:01 UTC
Parallelism
76/100
Blocked
53%
Avg conflicts / tx
0.8
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,192,136 · 25 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
2w03w14w25w38w411w112w514w015w119w521w122w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa235f717…e5c8
0xd32edf…ff58
11 touches
15 conflicts
0x64e1f0ce…7158
0x1b6862…e19c
4 touches
1 conflict
0x68531239…e9a3
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xbccdbd55…0f01
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x00000000…0012
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 0xa235f71788…b5e5c8
Audit this contract →
← previous block·next block →recent activity