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.
1895c2b693615928dd247a527adab968265ac64104f0a3b30adf8367998365a6
Both payments are on their chains and locked to the same secret hash 38bc48daf8487495e6a558d63c3015084c6cc733, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 1895c2b693615928dd247a527adab968265ac64104f0a3b30adf8367998365a6
- MakerPaymentSpent: 5f32b3310cd16abbb9e7d1634af18f81f5dfd00d2d5eae50a8473d28c22f8dc8
560859dd69470d3439a0d197bbc63636b33245c4f958c8c25d6cfb251dc93ba7
Both payments are on their chains and locked to the same secret hash 38bc48daf8487495e6a558d63c3015084c6cc733, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: cb41ba6021fae1f712711ec607b91d223687e5e1511adaaa40adebf31b77c7f3
- TakerPaymentSent · TakerPaymentReceived: 560859dd69470d3439a0d197bbc63636b33245c4f958c8c25d6cfb251dc93ba7
- TakerPaymentSpent: 77001aa6dd55f36b9d0c616250fefe737a526daf957526f5355d39aeb7ed291a
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.