← previous blocknext block →recent activity
Analyzing
Block #101,893,763
22 transactions · 21 stateful · 2026-09-04 11:53:05 UTC
Parallelism
73/100
Blocked
48%
Avg conflicts / tx
1.05
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,893,763 · 22 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
1w02w13w04w25w36w49w210w211w512w314w417w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd066be45…1d8c
0xd32edf…ff58
11 touches
15 conflicts
0x676f9f01…a8ac
0x34b655…2a6f
6 touches
3 conflicts
0x261cbea7…e35d
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0018
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0028
0x1b6862…e19c
4 touches
1 conflict
0xac79a0c7…be0f
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x08d31c28…d50f
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
15 conflicts on slot 0xd066be45ff…771d8c
Audit this contract →
← previous block·next block →recent activity