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.
d57d5160884d0104d625d8337422345a6cd801437dd21838384235911ff97348
Both payments are on their chains and locked to the same secret hash a24c60c3713b1aec60c55fdcc92cbef1aa716084, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: d57d5160884d0104d625d8337422345a6cd801437dd21838384235911ff97348
- MakerPaymentSpent: 9825898609f08d70e17f419b262d9f4332065e3ed6cff6156837fd483f088507
664430ab51ebbf4827776284c436b67cabaab85929391b424b2c6a7416429822
Both payments are on their chains and locked to the same secret hash a24c60c3713b1aec60c55fdcc92cbef1aa716084, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: e4fa666e05f0e24a94619821b63ee696eeccc980ae9fe3c3b9ddd6904b80bd6f
- TakerPaymentSent · TakerPaymentReceived: 664430ab51ebbf4827776284c436b67cabaab85929391b424b2c6a7416429822
- TakerPaymentSpent: e322cd5eb452d443ca9248834e30f672904ee6466fbecc73684e69fdeca4df61
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.