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.
722722d017755a89bdbd489bf5dd92352ad56798d557c84b8819e63524fa192a
Both payments are on their chains and locked to the same secret hash a5c7362845cdd0a923e88261efa0772b03a47d95, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 722722d017755a89bdbd489bf5dd92352ad56798d557c84b8819e63524fa192a
- MakerPaymentSpent: 09d9715bd4383d3bccb01e00a8cc19e7dad34efcb0d81738ed577e0e24801a9a
cc08198fbe00758e1c12d552024c8a619c417a6d81a83b2d4f2dbac202231236
Both payments are on their chains and locked to the same secret hash a5c7362845cdd0a923e88261efa0772b03a47d95, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 1ad338d3f2d7b506024d5f4e19b44916330e6afcd254b83bb682c54c8d6d3fac
- TakerPaymentSent · TakerPaymentReceived: cc08198fbe00758e1c12d552024c8a619c417a6d81a83b2d4f2dbac202231236
- TakerPaymentSpent: 09406e2e0bb432ed456a67ef4a492530bbe873ba72f7fb11d57643352ef89f78
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.