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.
bbec9c74690a1fee64ec1ee79b74834e2c64ba235750e0728623bf5ff7f59ca5
Both payments are on their chains and locked to the same secret hash e6a860a0bea862b1659825ff2ac17c574aec41e0, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: bbec9c74690a1fee64ec1ee79b74834e2c64ba235750e0728623bf5ff7f59ca5
- MakerPaymentSpent: fa32ddbe900eda523b5076f4cdebd458bf0d4663926d61cc9b529fc8d1e06521
8626eccbb52469988c5e317b0cffd82caba1ca654a15d945b9046862c7978407
Both payments are on their chains and locked to the same secret hash e6a860a0bea862b1659825ff2ac17c574aec41e0, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: cfc7e21524579e6ad231b692cae644124b14f50e17baa98e18b11c74c178902a
- TakerPaymentSent · TakerPaymentReceived: 8626eccbb52469988c5e317b0cffd82caba1ca654a15d945b9046862c7978407
- TakerPaymentSpent: cc90e7b5f022f1fcf21ec9fdb93701945cb8ebb27e7bfa2c9cb99cb34506da66
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.