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.
d94f0ecde99c2265c12ea21e3bed1e4025f2570e031863dcdbd60cea3a001314
Both payments are on their chains and locked to the same secret hash 3b87a68b87459d2e0021308f1535b948bad0f26d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: d94f0ecde99c2265c12ea21e3bed1e4025f2570e031863dcdbd60cea3a001314
- MakerPaymentSpent: 3bd86855f7a29fe440bc4bd4f4fad02f3ee4e92ee3093d25be7435c8a9b45e24
a244aa575db994562508ff3e99aa888a573a0b310fe36827df6683618f977ab6
Both payments are on their chains and locked to the same secret hash 3b87a68b87459d2e0021308f1535b948bad0f26d, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 01bf2adc81a9daa1340c3220f81e27c64356d906b0dc852f7bb8bf4ee2870a8f
- TakerPaymentSent · TakerPaymentReceived: a244aa575db994562508ff3e99aa888a573a0b310fe36827df6683618f977ab6
- TakerPaymentSpent: 9432430435ec1a8439f820e8732379903ef13aa1dd6d20b95863713afffa2923
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.