← previous blocknext block →recent activity
Analyzing
Block #101,973,813
20 transactions · 17 stateful · 2026-09-04 18:39:04 UTC
Parallelism
70/100
Blocked
41%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,973,813 · 20 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
1w02w13w25w37w010w411w512w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa9a1f775…dfc0
0xd32edf…ff58
11 touches
15 conflicts
0xdb8288e3…7979
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…001a
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002a
0x1b6862…e19c
4 touches
1 conflict
0xc2aacf41…54ff
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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
15 conflicts on slot 0xa9a1f77599…07dfc0
Audit this contract →
← previous block·next block →recent activity