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.
77d46a298d2a86ff004113c7b247711743176b6ca91b15ca4975396867386b01
Both payments are on their chains and locked to the same secret hash 3214ca1cf0623b162abbd9b84068bd9ddac8f6bc, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 77d46a298d2a86ff004113c7b247711743176b6ca91b15ca4975396867386b01
- MakerPaymentSpent: 67ae2ac3fa78f4f656ade1d5845996dc7449cf190828f2b19b9bf682b8ec5c29
da5e27d45fecfb3492c1b8024efd13d1ded7186abcb4835cd242a5f93423981a
Both payments are on their chains and locked to the same secret hash 3214ca1cf0623b162abbd9b84068bd9ddac8f6bc, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: aedd85c0a0337e142ffa303daec948e49e2fbe2ff45a7912b9430e265236de07
- TakerPaymentSent · TakerPaymentReceived: da5e27d45fecfb3492c1b8024efd13d1ded7186abcb4835cd242a5f93423981a
- TakerPaymentSpent: a5f1a15776b672a2a8f37ebe85b048aee348b84db8d5087f1bb1b41d291c7394
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.