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.
dc6bfefbbd17e68be9f60d0e1a2f7c4dcd220a3d1bfdf55b3bc57ddbf67c60e5
Both payments are on their chains and locked to the same secret hash 32ffedd64f9bfa804e319fc6ffa44c9e74e7060f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: dc6bfefbbd17e68be9f60d0e1a2f7c4dcd220a3d1bfdf55b3bc57ddbf67c60e5
- MakerPaymentSpent: a6019eb8547eb84a9d62d6f4a78299d24a298ab8a060140961b37e88e7bed063
aa5d2a151581203e746c4bdacea12d48cd06d102122aa3c83a9a54dcceb13c86
Both payments are on their chains and locked to the same secret hash 32ffedd64f9bfa804e319fc6ffa44c9e74e7060f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 3c98aff4440fd3a8227ca23a43e587c53bdfd2a3eb60241bffe59f38696115d2
- TakerPaymentSent · TakerPaymentReceived: aa5d2a151581203e746c4bdacea12d48cd06d102122aa3c83a9a54dcceb13c86
- TakerPaymentSpent: 29df044c813f36f3075d02a9d7486e4a332b8588e07a4b3234c5c210a7690cdc
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.