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.
6ed282a876e1104c89a8af1e8bb2fed2c2b4f9a5d66461fb8c32d8df3b617e22
Both payments are on their chains and locked to the same secret hash e1e64e474e35e4969843d2b018e526d9cb6f224f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 6ed282a876e1104c89a8af1e8bb2fed2c2b4f9a5d66461fb8c32d8df3b617e22
6693d2fef5ee5d031a29f59f3a996124b55fc99703ab63e488bc0366a182cfca
Both payments are on their chains and locked to the same secret hash e1e64e474e35e4969843d2b018e526d9cb6f224f, and a preimage hashing to it was published on chain when one side claimed.
- TakerPaymentReceived: 6693d2fef5ee5d031a29f59f3a996124b55fc99703ab63e488bc0366a182cfca
- TakerPaymentSpent: 111dac16a879204f6212f5e5dd1f38c02617dba137ca5c6f40b54ea67de9e44b
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.