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.
72d26ba963e6237c67772b06a5edae4cf60919bd08be6cffcd81180c0d51c7ec
Both payments are on their chains and locked to the same secret hash 2717750dee403a2c014a6011bbd45307ab0ff88d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 72d26ba963e6237c67772b06a5edae4cf60919bd08be6cffcd81180c0d51c7ec
7018336342e28b35302ee3907e138561c2d2dd56dea5f5bde6ecf81c1c53c749
Both payments are on their chains and locked to the same secret hash 2717750dee403a2c014a6011bbd45307ab0ff88d, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: ee719149e7ff66a32e211f0e0418e3911c8e3b3fda3a351b5d02a472e8de5d9d
- TakerPaymentReceived: 7018336342e28b35302ee3907e138561c2d2dd56dea5f5bde6ecf81c1c53c749
- TakerPaymentSpent: 6269e299b97ee314b564ab87518b85f5dbfa418bd1ea9f06758ea88302d1e8c3
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.