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.
500f457db7f6e01a9dcdda4db2cd42f7968a05d9d963cef246c53331fea2ffe5
Both payments are on their chains and locked to the same secret hash 64d5c5898d151cc9a644c8df9ae9fa7b9d0ddf33, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 500f457db7f6e01a9dcdda4db2cd42f7968a05d9d963cef246c53331fea2ffe5
- MakerPaymentSpent: a39dbebf1d7f7ca31015de31a4acd32dfc6fbc3af89288dd60d01c18caa8b7c8
c2698d4b8a1c4b28215dd43e811b1c2a2837d1663e2c67b9bc0ab25263d7e38d
Both payments are on their chains and locked to the same secret hash 64d5c5898d151cc9a644c8df9ae9fa7b9d0ddf33, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 34c030242af1ed6b7560bf0be174b1fe4d3583e413d5f668ae58a1d624d1c948
- TakerPaymentSent · TakerPaymentReceived: c2698d4b8a1c4b28215dd43e811b1c2a2837d1663e2c67b9bc0ab25263d7e38d
- TakerPaymentSpent: a267767f945ebe06d6d876d4c4ca205b93fdd5fe95a9150cf623059379c04d28
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.