← previous blocknext block →recent activity
Analyzing
Block #73,328,752
13 transactions · 9 stateful · 2026-05-08 22:11:58 UTC
Parallelism
77/100
Blocked
22%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,328,752 · 13 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
1w03w04w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f08361d…bda6
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x07304f39…c0a9
0xd32edf…ff58
3 touches
1 conflict
0x3b53fcac…abb9
0x065c9d…c394
2 touches
0 conflicts
0x3d690cbe…f721
0x065c9d…c394
2 touches
0 conflicts
0x401d62b2…d98e
0x065c9d…c394
2 touches
0 conflicts
0x70a0117f…e982
0x065c9d…c394
2 touches
0 conflicts
0xa4b48096…4bd3
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 0x6f08361da9…89bda6
Audit this contract →
← previous block·next block →recent activity