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.
50eb66612db832b236bec003dc14d23c828b4fe1f9061f5fafc7d844c6dfff6e
Both payments are on their chains and locked to the same secret hash 2429aadc2474c6b3804fe76d4e53fc026c101a4d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 50eb66612db832b236bec003dc14d23c828b4fe1f9061f5fafc7d844c6dfff6e
- MakerPaymentSpent: 08b445fceb343db9be4b39328867d3d984a2fb298e967401144177706965e868
8d6acc73d1cd0802a1d85fa2bf64b72e961065931f5a83be6ab8647ae288edf2
Both payments are on their chains and locked to the same secret hash 2429aadc2474c6b3804fe76d4e53fc026c101a4d, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: ff46b58751b8ab4681fc08702190f10a35087c5f972cc13a4c3c826ca68e198a
- TakerPaymentSent · TakerPaymentReceived: 8d6acc73d1cd0802a1d85fa2bf64b72e961065931f5a83be6ab8647ae288edf2
- TakerPaymentSpent: 2497ce03a360d39d24ef7748a10d05e55296c7c621f614ec57374472526bd6ad
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.