← previous blocknext block →recent activity
Analyzing
Block #72,314,237
27 transactions · 25 stateful · 2026-05-04 05:35:48 UTC
Parallelism
85/100
Blocked
56%
Avg conflicts / tx
1.07
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #72,314,237 · 27 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
2w03w15w07w08w09w210w311w012w113w014w115w216w318w119w221w222w223w324w326w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xb4f589da…a819
0xd32edf…ff58
7 touches
6 conflicts
0x24968e6d…0132
0x065c9d…c394
6 touches
3 conflicts
0xbbee74c2…567a
0x065c9d…c394
6 touches
3 conflicts
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0x17e2d2a0…359e
0x34b655…2a6f
6 touches
3 conflicts
0xb9d2cf20…a668
0x34b655…2a6f
6 touches
3 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity