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.
6761d457c793a44b2ba21521ca9485c0d85d302c9028a161f112ac0d7c4a62cd
Both payments are on their chains and locked to the same secret hash 84b3cd5e17badd834a50b04ba6ebaddd453cbad3, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 6761d457c793a44b2ba21521ca9485c0d85d302c9028a161f112ac0d7c4a62cd
- MakerPaymentSpent: 8e0c84a544e8e9ca21f740b47574d81554efee8e2356af0fc56fa6e44021d2a7
96cd20f434ddf04417c6d4615c7bd50292b52448068b1b658349d560d74f8697
Both payments are on their chains and locked to the same secret hash 84b3cd5e17badd834a50b04ba6ebaddd453cbad3, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: f6b747c0e3f5118682287d097fd02fc409265fa7eaff94e9cd13463ac2a8acb2
- TakerPaymentReceived · TakerPaymentSent: 96cd20f434ddf04417c6d4615c7bd50292b52448068b1b658349d560d74f8697
- TakerPaymentSpent: 9e006865eef85ab762e7c3d4228a6dc1632f654cd70396550062160b509d0b16
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.