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.
c985c6954cc9d6602b1e51808df05e7a5dd69f1fe61d60ee5a5c5591f5071e81
Both payments are on their chains and locked to the same secret hash 59f64cd43a0add3b647d3ac8e9fcb23095523c28, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: c985c6954cc9d6602b1e51808df05e7a5dd69f1fe61d60ee5a5c5591f5071e81
- MakerPaymentSpent: 353d9104a474bd5da29d5e2883f07f627b47cb3f01e60c95ee1c746a76be4f9b
0db9bf6587c0b36cb4f31b725e9b28ddb9b97c0b8dd51bb8d41efdb7a1ee4940
Both payments are on their chains and locked to the same secret hash 59f64cd43a0add3b647d3ac8e9fcb23095523c28, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 4a86c8f454b557bd35227ee768753dbccdee1a57fefae0097dccb49ad624ba3b
- TakerPaymentSent · TakerPaymentReceived: 0db9bf6587c0b36cb4f31b725e9b28ddb9b97c0b8dd51bb8d41efdb7a1ee4940
- TakerPaymentSpent: edc8315827b088fbaebb990ee5ccc45bcfdc9c54dd27b9e9741428f95ab7dc02
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.