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.
994615997d5584bd2e5204959ac660ed03f0f55336c748ff48354e2df7605fd1
Both payments are on their chains and locked to the same secret hash 70dc93ddef7ca3983ba83b3fb29aa5ee6109d4ad, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 994615997d5584bd2e5204959ac660ed03f0f55336c748ff48354e2df7605fd1
- MakerPaymentSpent: b1fd9bdad26b3a64cf38aeff3b08beb1f89f0a2e4e6a0cd868f75ec360f70ef7
feb5ed9007606544c20bbf043c3dfb19cea767d898b50a7e152058355768daf6
Both payments are on their chains and locked to the same secret hash 70dc93ddef7ca3983ba83b3fb29aa5ee6109d4ad, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 443e7097c080de330231bc71e049e459483ffc8501b680621c19c12fcd936626
- TakerPaymentSent · TakerPaymentReceived: feb5ed9007606544c20bbf043c3dfb19cea767d898b50a7e152058355768daf6
- TakerPaymentSpent: 1162bbd30b96c1b2498f80f3cde9bb90fa1ff47a001601b26f0a6069a3aa2b96
Reported by kdf-statsdb.