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.
764c295b0933b56ea62cc897a9d2540304e97eb086fe9799de7803b4bfe62911
Both payments are on their chains and locked to the same secret hash d5f4f870cd7d237ef5c535f4c95f849bf181df7c, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 764c295b0933b56ea62cc897a9d2540304e97eb086fe9799de7803b4bfe62911
- MakerPaymentSpent: a1cd6935984df22ef850b6ae0f57b9ccf4487d2c71bbe6e0c9eaca49da7a6a06
4ca8621a498c4d4761d7b64ebbdf2690a4ceee3d5bb283793f84e9135b95641e
Both payments are on their chains and locked to the same secret hash d5f4f870cd7d237ef5c535f4c95f849bf181df7c, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: d99bd23708024a5c97b09ab73dd9b4b5a381d4401955de0ea2103b2f05f8e36a
- TakerPaymentSent · TakerPaymentReceived: 4ca8621a498c4d4761d7b64ebbdf2690a4ceee3d5bb283793f84e9135b95641e
- TakerPaymentSpent: 4fd5088030ff63c1be4f90b958c13a356541e15a4e720d082a75f4141b12d4ce
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.