← previous blocknext block →recent activity
Analyzing
Block #72,286,304
30 transactions · 20 stateful · 2026-05-04 02:29:12 UTC
Parallelism
83/100
Blocked
50%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #72,286,304 · 30 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
1w02w13w24w37w09w010w116w219w020w121w223w128w329w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00bb3b64…90ae
0xd32edf…ff58
7 touches
6 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0xbad68552…e6bf
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0018
0x1b6862…e19c
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 0x00bb3b6447…f090ae
Audit this contract →
← previous block·next block →recent activity