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.
8c5ce8541544351678d20906206500473330eb330b856e93fcf491f78f65eb23
Both payments are on their chains and locked to the same secret hash 7dd20e0112246ec2029f6ac661daecae1decd645, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 8c5ce8541544351678d20906206500473330eb330b856e93fcf491f78f65eb23
- MakerPaymentSpent: 41729c07869ecd9e7aa834ee91c302026cadd38329df88eb8d344b386d716f98
3fc8aba0da5e483a58bdbb800cb5698d5253d5eac20ea385d60e824fede968b4
Both payments are on their chains and locked to the same secret hash 7dd20e0112246ec2029f6ac661daecae1decd645, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 83e226308baaad3081e19e1b5c846ad30781dd4fa98eea275548175d7490703e
- TakerPaymentSent · TakerPaymentReceived: 3fc8aba0da5e483a58bdbb800cb5698d5253d5eac20ea385d60e824fede968b4
- TakerPaymentSpent: f759635d9cb026ec2c807f3243c6ac3f836ce84a787609612c65716d68c92b4a
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.