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.
e5c665326d49d41b56248f900a145f9553ff5ec45d49b28fc0df13d318b38cf9
confirmed on-chain, locked to this swap's secret hash
- MakerPaymentReceived · MakerPaymentSent: e5c665326d49d41b56248f900a145f9553ff5ec45d49b28fc0df13d318b38cf9
- MakerPaymentSpent: 5cefbba3303e0c439c37dad7794dd1aea0d41f4bc181f8db0415f684d75d84a8
551f3417dd63bf34e221309affc18d6cbb437099605186b4c505bb265c4f39d9
hash not checked: 4 servers tried: 3 failed TLS verification, 1 refused the connection
- TakerFeeSent · TakerFeeValidated: b033a67f4a2fe660bb0a3d74b641066ba29189722905ce91395ad4df0dd4fe54
- TakerPaymentSent · TakerPaymentReceived: 551f3417dd63bf34e221309affc18d6cbb437099605186b4c505bb265c4f39d9
- TakerPaymentSpent: 2abfda56fa5d8caca83a5ea419c5ebaee7754683b9a25c07428ec3cc8da5a6db
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.