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.
4b4864757b9c4b5bfa136c1fa7dcabde56d0d768ae58ac54fd6d21b369bbbc3a
Both payments are on their chains and locked to the same secret hash 43e295d07665bd4519e9d3adfcde506d5c74c6fd, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 4b4864757b9c4b5bfa136c1fa7dcabde56d0d768ae58ac54fd6d21b369bbbc3a
- MakerPaymentSpent: e4a26c7e4066cd0d8ab9d458b340b8eed2f56f3c02bb69d67fd4696d46da0f6b
79c39a1794f3b376614dbf608a68cf9701e2e26225db677d56e6d1b5d1642084
Both payments are on their chains and locked to the same secret hash 43e295d07665bd4519e9d3adfcde506d5c74c6fd, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: fd30e94d98208016ef967beb33e916fef2c495bc50aca3e8fee53dc5f95ec2f3
- TakerPaymentSent · TakerPaymentReceived: 79c39a1794f3b376614dbf608a68cf9701e2e26225db677d56e6d1b5d1642084
- TakerPaymentSpent: 9fd3f5a93f75f53ff33ca23cc2ea5b1deba6e5ba035383ee1b18638a248d6b63
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.