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.
b5d610ea7bffe868ac1fe63aaab0e88025e6a6fd8127b64123b326acd32c4eb8
Both payments are on their chains and locked to the same secret hash ee221586aa8cf330e1d96f05bf115c9434bcb803, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: b5d610ea7bffe868ac1fe63aaab0e88025e6a6fd8127b64123b326acd32c4eb8
- MakerPaymentSpent: 3928818b4294fd5e2b7c30bfd46c52b24864c8d41c632be928df978ab2d87ec9
4f6bb4ebd521b193c802b9b5cc89445012bede95302a729f1a23b57064a283a4
Both payments are on their chains and locked to the same secret hash ee221586aa8cf330e1d96f05bf115c9434bcb803, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: b48c9386f7d05f107ebd4b1d547d291e51de1625bc379f2856ad2db951e6c3fb
- TakerPaymentSent · TakerPaymentReceived: 4f6bb4ebd521b193c802b9b5cc89445012bede95302a729f1a23b57064a283a4
- TakerPaymentSpent: 39931f5eac5c3ded9eb20729d0f827c60db5d0e9f2091d7a52fef5dccea66be0
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.