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.
ff42b70476cc6065cc1c01be477215924e46d2f6e3404bfd6c05f93ed171a448
Both payments are on their chains and locked to the same secret hash 4f2ee10940247f1a407de658d3d2e7b8028dcf2a, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: ff42b70476cc6065cc1c01be477215924e46d2f6e3404bfd6c05f93ed171a448
- MakerPaymentSpent: a1227eeb7ddb4582716389bc13b06065cf40081eb0fb1cc416bed66156d1bafe
cfa9bdc061bd5626b255baa3244f3b9d9d898f30c4f4e7f5deaf7141b4615850
Both payments are on their chains and locked to the same secret hash 4f2ee10940247f1a407de658d3d2e7b8028dcf2a, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: ac66810e27d2fb4302628cef6a26a770637483d81a3d76a6304bf672092eb8de
- TakerPaymentSent · TakerPaymentReceived: cfa9bdc061bd5626b255baa3244f3b9d9d898f30c4f4e7f5deaf7141b4615850
- TakerPaymentSpent: 5b88a98eda665f575e428786c98f4fcfaa33248bc84e92eb63f4cdb8e5e6900e
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.