← previous blocknext block →recent activity
Analyzing
Block #72,317,938
6 transactions · 5 stateful · 2026-05-04 06:00:26 UTC
Parallelism
50/100
Blocked
40%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #72,317,938 · 6 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd77c589…f3c3
0x065c9d…c394
6 touches
3 conflicts
0x0f5af2f0…bab8
0x065c9d…c394
5 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xe2d5933c…947d
0x065c9d…c394
3 touches
1 conflict
0xcccabc14…cbe4
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0004
0xd0f8a6…badc
2 touches
0 conflicts
0x09106a95…1467
0xeedfbc…f7dc
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
3 conflicts on slot 0xfd77c589c4…9ef3c3
Audit this contract →
← previous block·next block →recent activity