← previous blocknext block →recent activity
Analyzing
Block #72,171,406
17 transactions · 13 stateful · 2026-05-03 13:37:05 UTC
Parallelism
65/100
Blocked
54%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #72,171,406 · 17 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
1w02w13w24w35w48w510w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x786264f8…164e
0xd32edf…ff58
11 touches
15 conflicts
0xffe431af…8faa
0x065c9d…c394
4 touches
1 conflict
0xc3c8642a…7da5
0x2a68ba…90c5
4 touches
1 conflict
0xa8907a2d…2e21
0x065c9d…c394
3 touches
1 conflict
0xe49cb5b2…eca7
0x065c9d…c394
3 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…001e
0x1b6862…e19c
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
2 touches
0 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
15 conflicts on slot 0x786264f856…bf164e
Audit this contract →
← previous block·next block →recent activity