← previous blocknext block →recent activity
Analyzing
Block #101,148,776
24 transactions · 20 stateful · 2026-09-01 21:25:04 UTC
Parallelism
88/100
Blocked
20%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,148,776 · 24 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w17w09w110w011w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6b821ae8…4c6f
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0xf5dc501b…8313
0x34b655…2a6f
4 touches
1 conflict
0x6cd905d6…4116
0x40c49f…2af0
2 touches
0 conflicts
0x58a864a6…57e3
0x754704…b603
2 touches
0 conflicts
0xa0d3faac…ae01
0x754704…b603
2 touches
0 conflicts
0xa1087a5c…66c4
0x754704…b603
2 touches
0 conflicts
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
3 conflicts on slot 0x6b821ae8c3…5b4c6f
Audit this contract →
← previous block·next block →recent activity