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.
072447cb04dbe8d1f21684bdffbf6c7b7c7521a01567b0103b1a982403b2425d
Both payments are on their chains and locked to the same secret hash 48ec19da0631c607a5f79815e78aa2b390f3888b, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 072447cb04dbe8d1f21684bdffbf6c7b7c7521a01567b0103b1a982403b2425d
901825297dcad77dfa970d7bb94069b3532b972761608b7468e90974ed839cc4
Both payments are on their chains and locked to the same secret hash 48ec19da0631c607a5f79815e78aa2b390f3888b, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: cfa440452a3195a30b9fb73ad9b11e0ff5397c9f9182e9f82e0507bc79b51b17
- TakerPaymentReceived: 901825297dcad77dfa970d7bb94069b3532b972761608b7468e90974ed839cc4
- TakerPaymentSpent: d2feedff7b18782586c99a401a8b3f64f146c1a4e879c8ea54196e1525148cf9
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.