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.
1a5804cb612931569bde76266d5ae117dd02a666086eaa524885ba2943fd0209
Both payments are on their chains and locked to the same secret hash 0ff1e224770922fa76126657f495031ed043d3a2, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 1a5804cb612931569bde76266d5ae117dd02a666086eaa524885ba2943fd0209
4a375c80a0726bba11ded9643e90939a3bf5dbd8ecf18045e77f17ff7112e0e9
Both payments are on their chains and locked to the same secret hash 0ff1e224770922fa76126657f495031ed043d3a2, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 7d1d845556ab7ab0cc574b7aaedfdc428c61fc8312423472e60ffc2e56019112
- TakerPaymentReceived: 4a375c80a0726bba11ded9643e90939a3bf5dbd8ecf18045e77f17ff7112e0e9
- TakerPaymentSpent: 732ff99e53952e2770f9d18685eeb2502fe8dbef834feb4290fadfd18402da82
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.