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.
c233c7e99edbd3ac4b3c8722a244eda35af53d74216ca007d3ff7330bf2db29d
Both payments are on their chains and locked to the same secret hash dc217d43b1c5bc098779bad5ca2cfa25fadf3564, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: c233c7e99edbd3ac4b3c8722a244eda35af53d74216ca007d3ff7330bf2db29d
8b55573207d007a8a22920b6885da2a2010a7d4a88d31dae3bae71c98e0b1f14
Both payments are on their chains and locked to the same secret hash dc217d43b1c5bc098779bad5ca2cfa25fadf3564, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: c3afc0c6aebe9e274a87cbc5deca0ff227b3fbde0adca06ab7b5a700f7200a0f
- TakerPaymentReceived: 8b55573207d007a8a22920b6885da2a2010a7d4a88d31dae3bae71c98e0b1f14
- TakerPaymentSpent: 3d0488a235f1608c8330a30872ca5ae21e216b4876edf7f247cab1761877a57b
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.