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.
3ef0b6272261bd25d836aad7afc80c4b7c15ad218ce24d2f4b441aa56fef41cd
Both payments are on their chains and locked to the same secret hash 0a3171a66b3fb0c622e0b327e0f9e20f466f077c, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 3ef0b6272261bd25d836aad7afc80c4b7c15ad218ce24d2f4b441aa56fef41cd
- MakerPaymentSpent: 95f1d8e63a0d6c82b0490cf52f785911f1e366907f98301a2868d1c2567e25cd
01583bd153cf93d834ce241a578e71906099604832122c9fe76175890f469d51
Both payments are on their chains and locked to the same secret hash 0a3171a66b3fb0c622e0b327e0f9e20f466f077c, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: a03a2dca4a493ea9bc9df271c235a4d7bd6d31079f3948ddd8e50385b318327a
- TakerPaymentSent · TakerPaymentReceived: 01583bd153cf93d834ce241a578e71906099604832122c9fe76175890f469d51
- TakerPaymentSpent: d8adf157a42712bd24d44bc86af254ec822e8263ec0d72520fd28a24a5d3a19e
Reported by kdf-statsdb.