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.
fff4d0b1740ed476a6e9f02a4ce196d59615f837ff86b06cd9192010765cd788
Both payments are on their chains and locked to the same secret hash 9a822b5aa6c1123d71ef3b4493453d93786451b9, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: fff4d0b1740ed476a6e9f02a4ce196d59615f837ff86b06cd9192010765cd788
- MakerPaymentSpent: ebda4458dedbe6ea332c9047d229f62dde43f1836626380d5b7709292e344b61
7b94eb3492adefda26c8f6f89580c99ce61750e053b281bb3feb534acb775f2d
Both payments are on their chains and locked to the same secret hash 9a822b5aa6c1123d71ef3b4493453d93786451b9, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: d5e1bf264c39583522364636ad0ef01ded01894e4a2b0339632190aa2fd19924
- TakerPaymentSent · TakerPaymentReceived: 7b94eb3492adefda26c8f6f89580c99ce61750e053b281bb3feb534acb775f2d
- TakerPaymentSpent: 33b7902848d324d7142b045c34ce8c7c45520583cc40bcb6ba75ef9d166769b7
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.