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.
954515a59a88bc861228110fbf2513da86f9a6bb4792bd3fb0731f45f0799c85
Both payments are on their chains and locked to the same secret hash 094c136cf541a56f87b19e97cfb575aaf37dadb4, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 954515a59a88bc861228110fbf2513da86f9a6bb4792bd3fb0731f45f0799c85
- MakerPaymentSpent: 4ba0ad020d98f87b32c20027566c29c8aa991b597e914cc49a7e42b58962bc87
02bbaee4025f495c7615786da0d63e011eecbfc30ae658f8205250cc019a3e04
Both payments are on their chains and locked to the same secret hash 094c136cf541a56f87b19e97cfb575aaf37dadb4, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: d14c468c36afe574ee3fb623899f046e8b55780122b16f7f9fd4c19bc6e81d4c
- TakerPaymentSent · TakerPaymentReceived: 02bbaee4025f495c7615786da0d63e011eecbfc30ae658f8205250cc019a3e04
- TakerPaymentSpent: 7da40d59a0d180832380834aa433a6acef364acac9c2747914f30a1d5b307149
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.