← previous blocknext block →recent activity
Analyzing
Block #72,212,970
9 transactions · 9 stateful · 2026-05-03 18:16:24 UTC
Parallelism
78/100
Blocked
11%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,212,970 · 9 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
2w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb4d1cf96…e34d
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x5bcd3cc8…8c05
0x065c9d…c394
3 touches
1 conflict
0x9ec9cde7…1dc4
0x065c9d…c394
3 touches
1 conflict
0x2700abe0…293b
0x065c9d…c394
2 touches
0 conflicts
0x32b35373…e734
0x065c9d…c394
2 touches
0 conflicts
0x80d4eaa9…b1ca
0x065c9d…c394
2 touches
0 conflicts
0x88eb8876…6052
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 0xb4d1cf9661…c9e34d
Audit this contract →
← previous block·next block →recent activity