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.
bf6db6cd66050833d4ed484e050f3310f76bbbd1ee7727ac0ce26bd32c13e288
Both payments are on their chains and locked to the same secret hash 80079d02c35465daabe02a451ed2f671e219fc0f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: bf6db6cd66050833d4ed484e050f3310f76bbbd1ee7727ac0ce26bd32c13e288
- MakerPaymentSpent: baa39199136f00fd37060c54f46c6999f6afd41da7d28f0566ea1c069c1605aa
fef646de5eb27aae96e768a744661ff4205922ceb54378caba61c7527e8e3aad
Both payments are on their chains and locked to the same secret hash 80079d02c35465daabe02a451ed2f671e219fc0f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: b817f7681f547912033e9bc3133ef3bc642bbf69ccb219ccad85e2a542bfa5b9
- TakerPaymentSent · TakerPaymentReceived: fef646de5eb27aae96e768a744661ff4205922ceb54378caba61c7527e8e3aad
- TakerPaymentSpent: 1279507335453bed3b315792f258ab38cdec90e1718297ff9c16966457527976
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.