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.
1908ec2ab53aa3d4df71f1dabc6024e604c86c35f0ebfec1858675eb9b6d990e
Both payments are on their chains and locked to the same secret hash ab8b680b8574cb0ee07747735aa92fdfad653685, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 1908ec2ab53aa3d4df71f1dabc6024e604c86c35f0ebfec1858675eb9b6d990e
- MakerPaymentSpent: 60be19e8d3d66b3b3f3b06a40f05515f11b1d0bd9ebf54413962e2fa5ec1834a
9f6f588aa35b744499665740fecaacf60dcf151db2e70d4e7145b357ec5dfa18
Both payments are on their chains and locked to the same secret hash ab8b680b8574cb0ee07747735aa92fdfad653685, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: b1d1e397768b0f5d025c1bb753de8bf2d3718829ae5d769a3562b54a2fac3e90
- TakerPaymentSent · TakerPaymentReceived: 9f6f588aa35b744499665740fecaacf60dcf151db2e70d4e7145b357ec5dfa18
- TakerPaymentSpent: aed3969d531af3e3650a7767486aaf783ba2202ad8db2ee99094f649382a82df
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.