← previous blocknext block →recent activity
Analyzing
Block #99,183,284
30 transactions · 25 stateful · 2026-08-26 00:15:28 UTC
Parallelism
80/100
Blocked
48%
Avg conflicts / tx
0.8
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,183,284 · 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
1w02w13w25w09w010w111w214w016w317w418w219w323w125w128w429w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x408a7c6a…7e71
0xd32edf…ff58
9 touches
10 conflicts
0x7de57974…f5ba
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xd689a6a5…0d01
0x34b655…2a6f
6 touches
3 conflicts
0x511f46a7…edaa
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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
10 conflicts on slot 0x408a7c6a05…097e71
Audit this contract →
← previous block·next block →recent activity