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.
08493f9c681aea5b05e44de923015ffd3760132796e470d3d5bb317efc5c0dd5
Both payments are on their chains and locked to the same secret hash 6ebb1342cb72ae749a3874e17362028aba9d3cb9, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 08493f9c681aea5b05e44de923015ffd3760132796e470d3d5bb317efc5c0dd5
- MakerPaymentSpent: a21db9dde5bb5c516c4056d6d1da7e80b0f897d28d77b14a46a7a18a21b468df
fd74bdb44c7275504d5e72f2b8df1509c016e99234e347c25b884b5742795580
Both payments are on their chains and locked to the same secret hash 6ebb1342cb72ae749a3874e17362028aba9d3cb9, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 043dfbedaf34e4ad45e635326e557271ca1ebb3118f6b708df5e57538c3c0000
- TakerPaymentSent · TakerPaymentReceived: fd74bdb44c7275504d5e72f2b8df1509c016e99234e347c25b884b5742795580
- TakerPaymentSpent: f7016cf6a1ef9f772f409ae8afe6ad1b80c9287a75f0b9b42d469ea0bf7f4f03
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.