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.
6b9cd44ed1d026168c19c82bd35ee89d2d2b7c7fc53a2957bdecab767dd726ee
Both payments are on their chains and locked to the same secret hash 1c7e8cf5a815989d9e845efb5f35159c637feed9, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 6b9cd44ed1d026168c19c82bd35ee89d2d2b7c7fc53a2957bdecab767dd726ee
- MakerPaymentSpent: bcd04934140b0278e7030fdbcdae3416c58cc8a0d6a348888408157bdd7708d9
6a552ff4756010a133353fd59d0b2dc6a5f265371bdef70a768438ff500ac33d
Both payments are on their chains and locked to the same secret hash 1c7e8cf5a815989d9e845efb5f35159c637feed9, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 29f1c6e95c39eee6d2af6fac977121fcad9e34782e9307ca717332b7652162e3
- TakerPaymentReceived · TakerPaymentSent: 6a552ff4756010a133353fd59d0b2dc6a5f265371bdef70a768438ff500ac33d
- TakerPaymentSpent: 1899ae1924dc118f2da7df6089b99707f1cf12758f472791737a0cc8d1a95e2b
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.