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.
9933ce1b501b0223f4afaa3dbbc3be05a5c89d460718790943db908e56775b13
Both payments are on their chains and locked to the same secret hash a9bcc531042e235682a4c61c8ad8f3e7e5f2596f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 9933ce1b501b0223f4afaa3dbbc3be05a5c89d460718790943db908e56775b13
a4690e384f048a514ae64627dff36ccdf17a62d190d9324cb6362f55b3803577
Both payments are on their chains and locked to the same secret hash a9bcc531042e235682a4c61c8ad8f3e7e5f2596f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: e73c612192dd7c771f4c2b5c43e959191d2de673cad2721c5cf3b8a10ec61bfe
- TakerPaymentReceived: a4690e384f048a514ae64627dff36ccdf17a62d190d9324cb6362f55b3803577
- TakerPaymentSpent: ab8864e329392675ab7ba847e118b22c900b6b66fe240edae26f2ae85218a720
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.