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.
a787ff4f5d12b93e8ccf0404a3ed4eb6c024d1ef08b79308e83f8b9e98b13491
Both payments are on their chains and locked to the same secret hash a24e4d3ce21122779d4b78b4e70e23d1a4d73833, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: a787ff4f5d12b93e8ccf0404a3ed4eb6c024d1ef08b79308e83f8b9e98b13491
- MakerPaymentSpent: b3d70f7a5d6f127c340dbd68b3ab54b82a84374c16bce04daa5066184a41c805
d87d08c5423484262e05f95288c70f205cbdeb1f89fc3635b6a23a983f726b48
Both payments are on their chains and locked to the same secret hash a24e4d3ce21122779d4b78b4e70e23d1a4d73833, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 9a8fa17689f68cce29e521e7e0be8ae762d3c0ab32be6cd6229b9b8c3fcfbd01
- TakerPaymentSent · TakerPaymentReceived: d87d08c5423484262e05f95288c70f205cbdeb1f89fc3635b6a23a983f726b48
- TakerPaymentSpent: bc05265d1ffd6c5d23fe5f76f05a55e618e5a1f7ccd4db48c4f8a4728d26c4d6
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.