← previous blocknext block →recent activity
Analyzing
Block #73,029,446
15 transactions · 15 stateful · 2026-05-07 13:00:29 UTC
Parallelism
73/100
Blocked
33%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,029,446 · 15 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w16w27w313w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x051b7209…bd36
0x065c9d…c394
6 touches
3 conflicts
0x0b390c61…dc07
0x065c9d…c394
6 touches
3 conflicts
0x0f581a4a…b468
0x065c9d…c394
6 touches
3 conflicts
0x3a1d7033…1395
0x065c9d…c394
6 touches
3 conflicts
0x5cfaaedb…d89c
0x065c9d…c394
6 touches
3 conflicts
0xab516ca8…4804
0x065c9d…c394
6 touches
3 conflicts
0xbd7e37a9…9eb5
0x065c9d…c394
6 touches
3 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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity