← previous blocknext block →recent activity
Analyzing
Block #101,501,728
24 transactions · 20 stateful · 2026-09-03 03:00:57 UTC
Parallelism
83/100
Blocked
45%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,501,728 · 24 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w07w19w011w112w014w316w217w218w323w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x676f704e…45ea
0xd32edf…ff58
7 touches
6 conflicts
0x89999c15…fdac
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0018
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0028
0x1b6862…e19c
4 touches
1 conflict
0x17a7f697…dcb1
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…00c9
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 0x676f704e40…c145ea
Audit this contract →
← previous block·next block →recent activity