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.
2b3d89535ff7c7dabcf5651f3aa7c3114a38c338088b1f4448430998be755e7a
Both payments are on their chains and locked to the same secret hash a806c079b6f0a850304a2c1eff14b1189dc7ab90, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 2b3d89535ff7c7dabcf5651f3aa7c3114a38c338088b1f4448430998be755e7a
- MakerPaymentSpent: 567303daf6738a33aa12be286f47af82a0010a401529e20e789cf43177461b4e
141ba40912a0f1470cc1e7bcd20bc8a3ef08d4fdfcf0033e359402b9ea4d902f
Both payments are on their chains and locked to the same secret hash a806c079b6f0a850304a2c1eff14b1189dc7ab90, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 8f3a06559dcf9be0a1b8958ca979e28461a058f5c397fb2d191af83d41aab7b0
- TakerPaymentSent · TakerPaymentReceived: 141ba40912a0f1470cc1e7bcd20bc8a3ef08d4fdfcf0033e359402b9ea4d902f
- TakerPaymentSpent: 3315682ca66de620d039a439a4e31cdea926bda6bf0bf677b247f693a2624352
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.