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.
af9e18a64f48bb56cc6fa043669614090fe396f47a9b7cb0d01bbec4dae22237
Both payments are on their chains and locked to the same secret hash 564d9b7fecdb31b5a79670856e54bac25bf6d2d8, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: af9e18a64f48bb56cc6fa043669614090fe396f47a9b7cb0d01bbec4dae22237
- MakerPaymentSpent: 66f17828a1ea738b90662159ff57e05cee113db26733e7831d00643831c5f703
cd33702231ac9f698a9960b53de12544a2fa5c1f28fe31098dcffef9762258ad
Both payments are on their chains and locked to the same secret hash 564d9b7fecdb31b5a79670856e54bac25bf6d2d8, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 3849cc25267df5b725922eddc973880fab18f3ca9ca3bc79991dfef09c3e6ae9
- TakerPaymentReceived · TakerPaymentSent: cd33702231ac9f698a9960b53de12544a2fa5c1f28fe31098dcffef9762258ad
- TakerPaymentSpent: 1f4b1c0a76f7ea558331106ad57b00a5bfe71e308d7a418dd11cc678d07d2f56
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.