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.
286b7648f181d44075b746e9a8a711c2fa89f79fde7b9e6d12c9c9b7f1677d77
Both payments are on their chains and locked to the same secret hash 20f053507b22b1df7890a45acaa550dcd581b39c, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 286b7648f181d44075b746e9a8a711c2fa89f79fde7b9e6d12c9c9b7f1677d77
- MakerPaymentSpent: 1468cc0aa560d6de1c8942daa94e761fb078aafe0884b0f14ce1457702d4bed7
72260856b9aba2e91c2bc69f4cd03807dad705036d807c54628dc0f8baa48b1c
Both payments are on their chains and locked to the same secret hash 20f053507b22b1df7890a45acaa550dcd581b39c, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: ea91a0599458c3aa6c4accc66ac6d906fe66a52143c18f6b4ad5c547aa49960a
- TakerPaymentSent · TakerPaymentReceived: 72260856b9aba2e91c2bc69f4cd03807dad705036d807c54628dc0f8baa48b1c
- TakerPaymentSpent: 46b77ce4aa71bb42fee1c3450f992c9f20be9a64bdb11b4f480a8fd1860b455e
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.