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.
414960ec38670aed74757bfcc867822bcf68902a58b29c18c94022ea527f786e
Both payments are on their chains and locked to the same secret hash 2f84472fd7054ac1610364e6ae6a45b3284137e6, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 414960ec38670aed74757bfcc867822bcf68902a58b29c18c94022ea527f786e
- MakerPaymentSpent: 3179ff4211730e683fb4d82d0cb48f040f510296c380fff7d9dcb3559b032cc7
9da6014f57855cd710ab1ed5151bf054a99885fbaabc9deca18ff07619a5e336
Both payments are on their chains and locked to the same secret hash 2f84472fd7054ac1610364e6ae6a45b3284137e6, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 2496e272ae91b87643dca88892a11abe23f21d6cf6523fcfe969816d29f1f239
- TakerPaymentSent · TakerPaymentReceived: 9da6014f57855cd710ab1ed5151bf054a99885fbaabc9deca18ff07619a5e336
- TakerPaymentSpent: fcafdfd4a18548e6b9e58afeefcc51820b1919791bfd5ffb613ce6c4b55b9711
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.