← previous blocknext block →recent activity
Analyzing
Block #72,285,527
10 transactions · 9 stateful · 2026-05-04 02:23:58 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,285,527 · 10 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
1w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x88037a63…fd9b
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x43f7537d…1a7d
0x065c9d…c394
3 touches
1 conflict
0x090e8555…1760
0x065c9d…c394
2 touches
0 conflicts
0x22560693…ebfb
0x065c9d…c394
2 touches
0 conflicts
0x24968e6d…0132
0x065c9d…c394
2 touches
0 conflicts
0xb4aa52f0…0cc2
0x065c9d…c394
2 touches
0 conflicts
0xe88f8c89…4c9b
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 0x88037a63bc…65fd9b
Audit this contract →
← previous block·next block →recent activity