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.
4d04c424075addb92f8cae77874fb4debf61b3fbdaed05cfc146b526bcd0ad76
confirmed on-chain, locked to this swap's secret hash
- MakerPaymentSent · MakerPaymentReceived: 4d04c424075addb92f8cae77874fb4debf61b3fbdaed05cfc146b526bcd0ad76
- MakerPaymentSpent: fffa9e3bbcd6505f3a5d9bac2643377d1ba2188771c9bb763b6f82a580d25d0d
83ad2f1df1eae0a09f34094c6378dcb21e6c8abc4b8553b0878ed62a3eb93ada
hash not checked: 4 servers tried: 3 failed TLS verification, 1 refused the connection
- TakerFeeSent · TakerFeeValidated: 1500425493c5a57b726e1c7ecb2df24519dcedc32fae3cbcae1737d644f6a113
- TakerPaymentReceived · TakerPaymentSent: 83ad2f1df1eae0a09f34094c6378dcb21e6c8abc4b8553b0878ed62a3eb93ada
- TakerPaymentSpent: c1dc26a2ccde9d938a37dd923d15216fc03f0d3f3fd1ef449935d93df19bc468
No flags are stored against this swap. Flags are written while a swap sits inside a live pricing window, so on an older swap their absence means it was never assessed rather than that it was assessed and found clean.
Reported by kdf-statsdb-8762.