← previous blocknext block →recent activity
Analyzing
Block #72,365,553
10 transactions · 7 stateful · 2026-05-04 11:17:38 UTC
Parallelism
80/100
Blocked
14%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,365,553 · 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
2w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0c7ac0ef…cdd2
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xffe431af…8faa
0x065c9d…c394
4 touches
1 conflict
0x2a3761ad…ffda
0x065c9d…c394
3 touches
1 conflict
0x091a962a…8374
0x065c9d…c394
3 touches
1 conflict
0xe0c7d7b4…99de
0x065c9d…c394
3 touches
1 conflict
0x211c24c2…c0c2
0x065c9d…c394
3 touches
1 conflict
0x90a6030d…08e3
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 0x0c7ac0ef27…bccdd2
Audit this contract →
← previous block·next block →recent activity