← previous blocknext block →recent activity
Analyzing
Block #72,310,804
17 transactions · 13 stateful · 2026-05-04 05:12:56 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #72,310,804 · 17 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
2w03w07w08w19w210w311w415w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5cd0f6f…dfe7
0xd32edf…ff58
7 touches
6 conflicts
0x92d610a6…9a40
0x2a68ba…90c5
6 touches
3 conflicts
0xeb79e93b…1c7b
0x065c9d…c394
5 touches
3 conflicts
0xf823e97f…2ee6
0x065c9d…c394
4 touches
1 conflict
0x7b7bcac3…8fbf
0x34b655…2a6f
4 touches
1 conflict
0xcf3283ba…c9fa
0x065c9d…c394
4 touches
1 conflict
0xeefbd26a…c8d1
0x065c9d…c394
4 touches
1 conflict
0x6af306bb…2e81
0x3bd359…433a
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 0xf5cd0f6f2f…28dfe7
Audit this contract →
← previous block·next block →recent activity