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.
f734cf5d9d770e78bafbab0e777e0df26db146622946f82c0a63602205ee2ca5
Both payments are on their chains and locked to the same secret hash d5f3b076ef87fa575334f152a4b7271bd632c3b7, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: f734cf5d9d770e78bafbab0e777e0df26db146622946f82c0a63602205ee2ca5
- MakerPaymentSpent: 39710f7daeb9e31a34446a8431c8b0f4170867aec6c6844b6249e3771ce9ff4d
7aed89379601d4970acac9cac20acf69861d98b54a4387917137ccff7d14ee73
Both payments are on their chains and locked to the same secret hash d5f3b076ef87fa575334f152a4b7271bd632c3b7, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 9adf45febd14e00bee10686e344f8cf7c12af866b45740003bde300c17c94651
- TakerPaymentSent · TakerPaymentReceived: 7aed89379601d4970acac9cac20acf69861d98b54a4387917137ccff7d14ee73
- TakerPaymentSpent: 08bece06661ef1f0271884694eef030903c02c7327ed1421399683388fc8f8b4
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.