← previous blocknext block →recent activity
Analyzing
Block #96,023,054
20 transactions · 18 stateful · 2026-08-14 21:20:42 UTC
Parallelism
80/100
Blocked
44%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,023,054 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w25w36w18w09w110w216w017w118w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9aba6cc8…bb2c
0xd32edf…ff58
7 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0006
0x968279…9342
4 touches
1 conflict
0x0f6aef87…8137
0x34b655…2a6f
4 touches
1 conflict
0x177211e2…1c2d
0x754704…b603
4 touches
1 conflict
0x521a5982…a82a
0x754704…b603
4 touches
1 conflict
0x6fc3cf50…23c5
0x968279…9342
4 touches
1 conflict
0x6fc3cf50…23c6
0x968279…9342
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
6 conflicts on slot 0x9aba6cc81f…86bb2c
Audit this contract →
← previous block·next block →recent activity