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.
9945a78d9818686e8582c01ca29808d479794102accbc48466d931437ffbdfb0
Both payments are on their chains and locked to the same secret hash 9e5ed4b490123e21e539e6b36400e71fee40d384, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 9945a78d9818686e8582c01ca29808d479794102accbc48466d931437ffbdfb0
- MakerPaymentSpent: 9208a4ab609801cc9064879b0855042a98ac6ce6a94b8e2c818ffe70e4ede7f0
43014742bfc5aad5bc43120e72f94ec4cea9e9996d8662d4b1ae2bcf53ffb112
Both payments are on their chains and locked to the same secret hash 9e5ed4b490123e21e539e6b36400e71fee40d384, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 0b5f50c1faee64280419166289804f54d88312870553a6f958c289f5bce60714
- TakerPaymentSent · TakerPaymentReceived: 43014742bfc5aad5bc43120e72f94ec4cea9e9996d8662d4b1ae2bcf53ffb112
- TakerPaymentSpent: 1f98d723e105ac4c3637216404ae2ae2bf49fc42241831a33b6c3bee91c0866e
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.