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.
67146db54a8ab6458b731531d44451ccd4be732eb46688975a1cad11d15d9d3c
Both payments are on their chains and locked to the same secret hash 512541233d833b0f171288102ab18fe2cbcb1de8, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 67146db54a8ab6458b731531d44451ccd4be732eb46688975a1cad11d15d9d3c
- MakerPaymentSpent: 4f029ce977767374c89b0e818391d7b0fb67fa67d0612391f86dd49db72c4501
eae95f3d0024ccd1ed853cf4f4a04e378f180ee890a78e96c914649cb79e90b3
Both payments are on their chains and locked to the same secret hash 512541233d833b0f171288102ab18fe2cbcb1de8, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: ead96dba8739a2d0cc2bbbf0625e279cf9242518b6859d63181d1c67551584d9
- TakerPaymentSent · TakerPaymentReceived: eae95f3d0024ccd1ed853cf4f4a04e378f180ee890a78e96c914649cb79e90b3
- TakerPaymentSpent: cd6a050fd13827307838c5bf84a3bce43617358e30783a926f584e00a9c66814
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.