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.
bf47f5872cbce67bab4c64ccc94744fdd5db0c496d45965684b289eccc77193c
Both payments are on their chains and locked to the same secret hash f973370c4d22575a76a2ce46b2eadcff9ff52fa5, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: bf47f5872cbce67bab4c64ccc94744fdd5db0c496d45965684b289eccc77193c
- MakerPaymentSpent: 0cd2f6f4d5ead888463b5fdb14ae7868b5ae4b8c151603e99370ff46656a114e
94d51d440ae37232a2088dfad5cbf2fbaadd636fec6338f72ce393808acf3ace
Both payments are on their chains and locked to the same secret hash f973370c4d22575a76a2ce46b2eadcff9ff52fa5, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: deae409902150a763509467d7ce7563d29541a06bfb78d7776e062508d901447
- TakerPaymentSent · TakerPaymentReceived: 94d51d440ae37232a2088dfad5cbf2fbaadd636fec6338f72ce393808acf3ace
- TakerPaymentSpent: 673ad8ea9aab00111554fcac6c7cd3bd2d2ebf14982cff0b60d2989000b4f7ae
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.