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.
e5529d6f05fd742e084aafb963dc180bb3becb9bc63fdf3c6a88b00e5c39a89e
Both payments are on their chains and locked to the same secret hash 6f0ef1e73708c88ac476c774ec722da42dad2de7, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · e5529d6f05fd742e084aafb963dc180bb3becb9bc63fdf3c6a88b00e5c39a89e
59678d6d2fa3b9b4c3d63b4799f4b4fe90ffd6e06a556c6a318616ba4d43051c
Both payments are on their chains and locked to the same secret hash 6f0ef1e73708c88ac476c774ec722da42dad2de7, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · aa6215b9cc344867917a81ea39b010d3905221d3b967d76265d060d3b5b25e49
- TakerPaymentReceived · 59678d6d2fa3b9b4c3d63b4799f4b4fe90ffd6e06a556c6a318616ba4d43051c
- TakerPaymentSpent · 429a028f7e869b41c317ae3c04e596c798aa5f4b4c85a48715bd76c701b97c9f
No anomalies were recorded against this swap.
Reported by kdf-statsdb.