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.
70bd62b1c98981add96460caae3670d94b0b4a113aab2093289a002c31105be6
Both payments are on their chains and locked to the same secret hash 446a6c2523629374518b4386072860f7658e0c24, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 70bd62b1c98981add96460caae3670d94b0b4a113aab2093289a002c31105be6
- MakerPaymentSpent: adfd247518927f06dfebd94daeb39a0d471648daff6e6d9c582edcbf5946c426
8951b149cd37631fe792c2caa87777f50f718b1f6d695faed489099da4905f4f
Both payments are on their chains and locked to the same secret hash 446a6c2523629374518b4386072860f7658e0c24, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 99f8407ff20242023257a49ce75bf6ecb0a40373fcd6adec5a01c92c4f54fe21
- TakerPaymentSent · TakerPaymentReceived: 8951b149cd37631fe792c2caa87777f50f718b1f6d695faed489099da4905f4f
- TakerPaymentSpent: 89a01655acc94c3658876d1da26879c24534ec8f2c5b7b56900627cfed640763
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.