← previous blocknext block →recent activity
Analyzing
Block #101,502,069
24 transactions · 22 stateful · 2026-09-03 03:02:40 UTC
Parallelism
79/100
Blocked
55%
Avg conflicts / tx
0.75
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,502,069 · 24 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
1w02w03w14w26w28w010w111w112w114w319w220w321w422w223w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8138ce5c…c203
0xd32edf…ff58
7 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x5934b407…e058
0x34b655…2a6f
4 touches
1 conflict
0x59adf3e4…b0f2
0x34b655…2a6f
4 touches
1 conflict
0x69d2053b…935a
0x34b655…2a6f
4 touches
1 conflict
0x7c8cf338…6e72
0x34b655…2a6f
4 touches
1 conflict
0x7dd96c96…7335
0x34b655…2a6f
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 0x8138ce5c64…17c203
Audit this contract →
← previous block·next block →recent activity