← previous blocknext block →recent activity
Analyzing
Block #101,801,868
16 transactions · 14 stateful · 2026-09-04 04:10:43 UTC
Parallelism
69/100
Blocked
57%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,801,868 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w26w38w310w313w415w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0c5cedf9…2b00
0xd32edf…ff58
9 touches
10 conflicts
0x78cb41e1…f2c1
0xfa32f9…f3f0
6 touches
3 conflicts
0xea2d3331…6e37
0x1b6862…e19c
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x99f666e3…b2a2
0x3bd359…433a
6 touches
3 conflicts
0x9194f4a3…10b8
0x754704…b603
6 touches
3 conflicts
0x00000000…0000
0xfa32f9…f3f0
6 touches
3 conflicts
0x00000000…0001
0xfa32f9…f3f0
6 touches
3 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
10 conflicts on slot 0x0c5cedf99d…282b00
Audit this contract →
← previous block·next block →recent activity