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.
5c9f7a298f7cbd4e976bce33eacef14319f61c46578806dbd31d00a9f3cc7b50
Both payments are on their chains and locked to the same secret hash 191bc8fa4320a0b482ed51c8ee459b6e76779560, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 5c9f7a298f7cbd4e976bce33eacef14319f61c46578806dbd31d00a9f3cc7b50
- MakerPaymentSpent: df4d77685f7af211c77d3b29e7e9ee02c34eae77b543f02869cdeb1d6558c95e
d044782578733f9f9ee5c2f3ad7c67afdc40c2e240ea2e2f9313d89d86aa04e3
Both payments are on their chains and locked to the same secret hash 191bc8fa4320a0b482ed51c8ee459b6e76779560, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: b4378cefa89864ff36d2c8aba746e624db8ddff02ad5ae0ded8b733a5bc8a54d
- TakerPaymentSent · TakerPaymentReceived: d044782578733f9f9ee5c2f3ad7c67afdc40c2e240ea2e2f9313d89d86aa04e3
- TakerPaymentSpent: 5cbe9edad7a3c376fc3addd27e1a273b636ee86f0a7318af770c7748cfb93207
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.