← previous blocknext block →recent activity
Analyzing
Block #101,501,735
21 transactions · 19 stateful · 2026-09-03 03:00:59 UTC
Parallelism
76/100
Blocked
53%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,501,735 · 21 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
1w02w13w24w35w06w17w012w213w014w116w117w218w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x39aabd5c…aa2c
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0018
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0028
0x1b6862…e19c
6 touches
3 conflicts
0xba5743c7…21bf
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
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 0x39aabd5c66…92aa2c
Audit this contract →
← previous block·next block →recent activity