← previous blocknext block →recent activity
Analyzing
Block #73,490,060
9 transactions · 7 stateful · 2026-05-09 16:05:20 UTC
Parallelism
78/100
Blocked
14%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,490,060 · 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
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e295f5…1bef
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0778eeca…ddb2
0x065c9d…c394
2 touches
0 conflicts
0xbd028ae7…01b5
0x065c9d…c394
2 touches
0 conflicts
0xc4612d4a…afe1
0x065c9d…c394
2 touches
0 conflicts
0xd7e42a8d…990f
0x065c9d…c394
2 touches
0 conflicts
0xd8a776a9…1269
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
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 0x22e295f5d8…ac1bef
Audit this contract →
← previous block·next block →recent activity