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.
fd5e2e3e21900729051302e1be809ce1a4afdd7472fdd395a4b05dad01dad9fd
Both payments are on their chains and locked to the same secret hash 2497c9a5100bd4bf794ee3995895921e26731882, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: fd5e2e3e21900729051302e1be809ce1a4afdd7472fdd395a4b05dad01dad9fd
- MakerPaymentSpent: 143182066cc8b4646a5b2d45bfbaa8cbd94487bda6da42f1f47ad0bd53237d73
21665abb132c66f218f8773f7f6293efe1435892bc801a64ea1cd7a41fbfb73e
Both payments are on their chains and locked to the same secret hash 2497c9a5100bd4bf794ee3995895921e26731882, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 29c45d193a844f546a6c49f4c7cb95d1aff3ad153db8a91f4e5a21a291e155d6
- TakerPaymentSent · TakerPaymentReceived: 21665abb132c66f218f8773f7f6293efe1435892bc801a64ea1cd7a41fbfb73e
- TakerPaymentSpent: e37878db405c311746aaa0de64353158963190d49a0d8ad16926cf8cfe35c02c
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.