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.
d009af2c5167c1d6c378fc18f450573f2420b02b29469f914e3a015683741505
Both payments are on their chains and locked to the same secret hash 58fae4a8c7acbfbca09a8a5750ef445752ad166e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: d009af2c5167c1d6c378fc18f450573f2420b02b29469f914e3a015683741505
- MakerPaymentSpent: f83f32296a1fca38187039194ee8e6d948dfc38ab1eb65e60a7e4feabd41df62
6dd150d35b57715c6d45e82c1871cc20a45443226d2c89801ea4fec2412bbf46
Both payments are on their chains and locked to the same secret hash 58fae4a8c7acbfbca09a8a5750ef445752ad166e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: cad7e4a0e071787cc164aaed42985f1865d6469a9bdd91f0f420f1526b385bd0
- TakerPaymentSent · TakerPaymentReceived: 6dd150d35b57715c6d45e82c1871cc20a45443226d2c89801ea4fec2412bbf46
- TakerPaymentSpent: 8395799c8682de1cfc9908658f6ac3137e30adc00422b16596bdf88af2dda77e
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.