← previous blocknext block →recent activity
Analyzing
Block #73,216,080
7 transactions · 5 stateful · 2026-05-08 09:42:17 UTC
Parallelism
71/100
Blocked
20%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,216,080 · 7 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
0x93336f10…35f6
0x065c9d…c394
4 touches
1 conflict
0x72f6718f…1bee
0x065c9d…c394
3 touches
1 conflict
0x0b390c61…dc07
0x065c9d…c394
2 touches
0 conflicts
0x0db74d28…23da
0x065c9d…c394
2 touches
0 conflicts
0x522cdec1…f274
0x065c9d…c394
2 touches
0 conflicts
0x650bd02e…1771
0x065c9d…c394
2 touches
0 conflicts
0x8e8978fe…2301
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