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.
aaea9662e270da4d619da007ff4ba4bf45ce958f1ef23aa51d3dda53ef6be168
Both payments are on their chains and locked to the same secret hash 10b90e62b1918766c9d13b99e29cd2a0813bf5c7, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: aaea9662e270da4d619da007ff4ba4bf45ce958f1ef23aa51d3dda53ef6be168
- MakerPaymentSpent: 0ef1498505cdbefeceec8123e9eed6d9f9a5f36aa5bc8fa4c34dedbe19bdb15f
c220c91d72c120d1e18f8520092c7595d62b358fd0479be0b9fa0e05fbc22035
Both payments are on their chains and locked to the same secret hash 10b90e62b1918766c9d13b99e29cd2a0813bf5c7, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: a7d458444943edf678c934948f7bb91c285858e515f795d3d031656c7cdfde5a
- TakerPaymentSent · TakerPaymentReceived: c220c91d72c120d1e18f8520092c7595d62b358fd0479be0b9fa0e05fbc22035
- TakerPaymentSpent: 86073110051b660adfb7da18962825a16be8cdcf2db73b5ed22b6ff7b1925b13
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.