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.
c5d520097960a37963c1b97d6002b193cb04448e15b1064bd412c6b62f3f471c
Both payments are on their chains and locked to the same secret hash 2a9d2eaf5a2daddf68cadccc8144d99226569cac, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: c5d520097960a37963c1b97d6002b193cb04448e15b1064bd412c6b62f3f471c
1b0608bec7fcf9b5ba32ca87cc649e7e34eebda599cf58d85ac935542225b9c1
Both payments are on their chains and locked to the same secret hash 2a9d2eaf5a2daddf68cadccc8144d99226569cac, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 5fca74bf12f2320f27b859b6ded59df2360cdf1b181755637ab9f1ded2d1dd6a
- TakerPaymentReceived: 1b0608bec7fcf9b5ba32ca87cc649e7e34eebda599cf58d85ac935542225b9c1
- TakerPaymentSpent: 2ba8d35ce5e0bc89d6fb323b629a70e3cd1e62aacba1995326646536105a7fe7
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.