← previous blocknext block →recent activity
Analyzing
Block #72,310,972
6 transactions · 5 stateful · 2026-05-04 05:14:03 UTC
Parallelism
67/100
Blocked
20%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,310,972 · 6 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x97d4d7c8…caf0
0x065c9d…c394
4 touches
1 conflict
0x0b6b8b2f…29e5
0x065c9d…c394
4 touches
1 conflict
0x72162d30…f098
0x065c9d…c394
3 touches
1 conflict
0x08ce5522…e456
0x065c9d…c394
3 touches
1 conflict
0x1e151f6d…2785
0x065c9d…c394
3 touches
1 conflict
0xbcadbe3f…cbe4
0x065c9d…c394
2 touches
0 conflicts
0xfa140438…5620
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity