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.
0bdc86bccea044fe81ccb98c957bfeaa89c4b5bc60f757c1f03c0de746b15a0d
Both payments are on their chains and locked to the same secret hash fbfba0c885d297362eb2a6ab11b8d935db158f9b, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 0bdc86bccea044fe81ccb98c957bfeaa89c4b5bc60f757c1f03c0de746b15a0d
- MakerPaymentSpent: 41117a612ad7feaed6ae81f55cc85ecee9cb567decc11f2e2de6763af5cc16bf
6bdfaab748f180b8d6e0ac3b3c8bfe789e49f4138324bf1f35a1910c0a919b29
Both payments are on their chains and locked to the same secret hash fbfba0c885d297362eb2a6ab11b8d935db158f9b, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 1efe0fdc4d6a18527c906bfc962448b6245b51620de1fe0be4c79f75fc51af56
- TakerPaymentSent · TakerPaymentReceived: 6bdfaab748f180b8d6e0ac3b3c8bfe789e49f4138324bf1f35a1910c0a919b29
- TakerPaymentSpent: fb0d56cebd1b8eec83fec2d908881872fc53130948d3ff991c8e716af1baf73c
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.