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.
052c39e6357aabfb2c06585ba5626aeca9725077f390387e2a4fd193379f5569
Both payments are on their chains and locked to the same secret hash 508b4378c550120b565bee1732ee11d1da46d8f3, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 052c39e6357aabfb2c06585ba5626aeca9725077f390387e2a4fd193379f5569
- MakerPaymentSpent: a2c4f524ab7b527bc5f3ae5dd5e28353371a66c36dd5e32946287884ab4a00b4
985844709eb47f41706ea452d6f4335047af9ae74f0a7ae7f442e8470387c729
Both payments are on their chains and locked to the same secret hash 508b4378c550120b565bee1732ee11d1da46d8f3, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: d68adde611217f8f7299ebc475d815d97a5d15528b70cb477cb61027e7f2f5e1
- TakerPaymentSent · TakerPaymentReceived: 985844709eb47f41706ea452d6f4335047af9ae74f0a7ae7f442e8470387c729
- TakerPaymentSpent: 480f9657d4cf78892f347d42f176e7d9fa6a4843013268ce8b13b9bf5c9a7e06
Reported by kdf-statsdb-8762.