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.
008f1f8bb5f1c27ad35a7dfb6769b405f08600c121df50387b5e994ec499579b
Both payments are on their chains and locked to the same secret hash cb118b6f22bc33216ca0dfb7f459daedac770302, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 008f1f8bb5f1c27ad35a7dfb6769b405f08600c121df50387b5e994ec499579b
- MakerPaymentSpent: 8d588be58116293694c5b8723618cabcd3b0cd15f3a723b93d918f6edbe0e738
75728b8ba9375b71f9857634b676578f4f34dbb5c61fd37ad8a88eb00460a272
Both payments are on their chains and locked to the same secret hash cb118b6f22bc33216ca0dfb7f459daedac770302, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: cc14ec0f009cfa72847d382a8938a25bc28e2cbc9f8cbe0fc10fb14e97e4c9cc
- TakerPaymentSent · TakerPaymentReceived: 75728b8ba9375b71f9857634b676578f4f34dbb5c61fd37ad8a88eb00460a272
- TakerPaymentSpent: a9a2867167845c389671a49a5e530413922c0270e63f6b2a9e502f3be75a0232
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.