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.
9f409fed88fbc6a8d16285bcb5ab4353ae5d51235942a2343d0ddc09fa72a91d
Both payments are on their chains and locked to the same secret hash d7993692da2f3b36a7e7e4a9abaa61a8b2d69afd, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 9f409fed88fbc6a8d16285bcb5ab4353ae5d51235942a2343d0ddc09fa72a91d
b0f0d12d576cff27be5b5e187d069cd256d960709c6f32a071816a0117c9befd
Both payments are on their chains and locked to the same secret hash d7993692da2f3b36a7e7e4a9abaa61a8b2d69afd, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 6297164bfe78f9e3d79f0012ddc49328b097760fc68cc577b2068e9ba358ad87
- TakerPaymentReceived: b0f0d12d576cff27be5b5e187d069cd256d960709c6f32a071816a0117c9befd
- TakerPaymentSpent: 4102cd9ed7d66a48c8d341cc1d893c702ec0e8e93e1b82c8b7b8723342337df5
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.