An atomic swap is not instant by design. Each side has to publish a transaction and wait for the other chain to confirm it, so the time it takes is set mostly by the block spacing of the two chains involved rather than by anything either party does.
69d3713251a2b54664cc9797d92b46dd8e6b0e27fa14d955fb497d69a9c7f85a
Both payments are on their chains and locked to the same secret hash c3706edf9a9c9e949e541d2265734e74f074121d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 69d3713251a2b54664cc9797d92b46dd8e6b0e27fa14d955fb497d69a9c7f85a
405c6fcd37dea79b3a70dc9e04cd12d82cf00b6cc7ad13a36481f08462329199
Both payments are on their chains and locked to the same secret hash c3706edf9a9c9e949e541d2265734e74f074121d, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · 17d9f368e5e7d68886af23ce427915777313738815ba142e63765c6080c4d605
- TakerPaymentReceived · 405c6fcd37dea79b3a70dc9e04cd12d82cf00b6cc7ad13a36481f08462329199
- TakerPaymentSpent · e0b3caa89d32d0ce9e8e6e922cf28ee1320e083352219c8131c0167acd46763b
No anomalies were recorded against this swap.
Reported by kdf-statsdb-8762.