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.
79d2b6727a216ed5482dfc7c4ef68e2d6fbbad81a04928c880d1463e46e8d5ba
Both payments are on their chains and locked to the same secret hash d7ffd09c3f108684e4d158ccd0e1dc6e2dc1e8e9, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 79d2b6727a216ed5482dfc7c4ef68e2d6fbbad81a04928c880d1463e46e8d5ba
- MakerPaymentSpent: e8ad50db4276d3c1ab1bcae8845395214ebaa3ac0965a54cd09271c0970f2e7f
0d790fcc9e86d10fa43ba2658882e5c6140be8fa8383d6d47e0a40d70992278a
Both payments are on their chains and locked to the same secret hash d7ffd09c3f108684e4d158ccd0e1dc6e2dc1e8e9, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 7bc0cf555d47164e7db87ea39fbaf51f26b009484c991ad24e2f226c89f56642
- TakerPaymentSent · TakerPaymentReceived: 0d790fcc9e86d10fa43ba2658882e5c6140be8fa8383d6d47e0a40d70992278a
- TakerPaymentSpent: acdd1ce4d558b563ad0fccb5d305ce8cc9263d41a2f6b55e7f046fa08633f35a
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.