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.
6576d86c33d347c562b0d95eccc352b2765d2ad899bc898b29caba687a439e42
Both payments are on their chains and locked to the same secret hash c5c2c0f14546b2884819bb6e1bf83fc31f51942e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 6576d86c33d347c562b0d95eccc352b2765d2ad899bc898b29caba687a439e42
- MakerPaymentSpent: a69ce809eedcbe51b6b6fcc5b8520f23630f9c615ae8a700d82838402c804ea3
5370c4cc1afa77e8924fc51d4dd55f955074f22771d8023dd3f732135d57ab43
Both payments are on their chains and locked to the same secret hash c5c2c0f14546b2884819bb6e1bf83fc31f51942e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: cef4fc8a5052863b05bda324767af571fb8d98e7c0b45aadd8b0ea4c50843ec1
- TakerPaymentSent · TakerPaymentReceived: 5370c4cc1afa77e8924fc51d4dd55f955074f22771d8023dd3f732135d57ab43
- TakerPaymentSpent: 6dd94073cedf7e038bfda6799031a2527d1d41ed8ac3761d46486dd53bcab9d5
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.