← previous blocknext block →recent activity
Analyzing
Block #72,317,947
13 transactions · 10 stateful · 2026-05-04 06:00:30 UTC
Parallelism
85/100
Blocked
20%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,317,947 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w08w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcccabc14…cbe4
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xb9d2cf20…a668
0x34b655…2a6f
4 touches
1 conflict
0x2fa48ddf…c5f0
0x065c9d…c394
3 touches
1 conflict
0xef92a10a…f8d9
0x065c9d…c394
3 touches
1 conflict
0x84b44ed4…4330
0x065c9d…c394
2 touches
0 conflicts
0x92e61a63…2bdc
0x065c9d…c394
2 touches
0 conflicts
0xbbee74c2…567a
0x065c9d…c394
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: Kuru Exchange: Market-MON/USDC
1 conflict on slot 0xcccabc145c…b4cbe4
Audit this contract →
← previous block·next block →recent activity