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.
c90efa7397874f8c505cc627b5bfdc863c53f6f79a11a8ec67af77af60212c7a
Both payments are on their chains and locked to the same secret hash bd3c0af5f19c8cf60f413bed120899587fe9a199, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: c90efa7397874f8c505cc627b5bfdc863c53f6f79a11a8ec67af77af60212c7a
- MakerPaymentSpent: 55000e362e470bc7d29c281e1df04b5f430d06e25881a9db26c3b10f6ceb228a
375bcdb83bbf970305b6a8214db6b314194e0282ce23c59666c30e70b113ea3f
Both payments are on their chains and locked to the same secret hash bd3c0af5f19c8cf60f413bed120899587fe9a199, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 547abbcbb87362ce11b6d2b21515d8f7c67cd682ed662bdd190a6a83a1775669
- TakerPaymentSent · TakerPaymentReceived: 375bcdb83bbf970305b6a8214db6b314194e0282ce23c59666c30e70b113ea3f
- TakerPaymentSpent: f7ecbf9236f93d9312e49210cad36305ed1f95edb2654c2851ac3551c2f58a59
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.