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.
9cb545674dff25b99741b3e9d1aec455faf1e68eff4cbff5845dcc055dde9966
Both payments are on their chains and locked to the same secret hash 425c654647bffabe599929041bd5b2f3aa971748, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 9cb545674dff25b99741b3e9d1aec455faf1e68eff4cbff5845dcc055dde9966
- MakerPaymentSpent: 57a6c3f8f2f1d79f15ef28c989745bfb49683eed9e32c819af803a69cc67e08b
aa3d315cae025f3b4cd3b305a22ee366ea62b9d078e61c4e0ad0094fa1bdc2cb
Both payments are on their chains and locked to the same secret hash 425c654647bffabe599929041bd5b2f3aa971748, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 37c8f406a1b993108af89efd0b0a7805de41bbc7bc00c21673219cf7e0445060
- TakerPaymentSent · TakerPaymentReceived: aa3d315cae025f3b4cd3b305a22ee366ea62b9d078e61c4e0ad0094fa1bdc2cb
- TakerPaymentSpent: 1e604d3e11a3e7148f4c132c8fa9a559d6ae6dbd68650338fd2a408a66fe1c56
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.