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.
658f866192d970671d4cf1ef23b00b3e9b8277898d299c66c3a380ffd0ed0c64
Both payments are on their chains and locked to the same secret hash 1318fd3a7a3d5f21c91ad0f8a41f41e331c6422a, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 658f866192d970671d4cf1ef23b00b3e9b8277898d299c66c3a380ffd0ed0c64
0a7bd96667accdef21833cdc34447e18d4096e88c149e12da8ea6dd31ba78d7b
Both payments are on their chains and locked to the same secret hash 1318fd3a7a3d5f21c91ad0f8a41f41e331c6422a, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 68b2ae168ba19cc7aa791b498a95b297738f579c83b810a3364a37a7fda8f47a
- TakerPaymentReceived: 0a7bd96667accdef21833cdc34447e18d4096e88c149e12da8ea6dd31ba78d7b
- TakerPaymentSpent: 49aa0e08e3c0f88f9046c529ad9d36d39a1ba8009a6d76318a720bb38f3ea9b8
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.