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.
108ef763bdc270fb7faaaf1c34b6cd101df74b778ba9cd300f194eb811ae8695
Both payments are on their chains and locked to the same secret hash 1ac9a92b6727678bf3710d3b80cb86e6497e7cbf, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 108ef763bdc270fb7faaaf1c34b6cd101df74b778ba9cd300f194eb811ae8695
- MakerPaymentSpent: bb491671adcdbc7ada39aee9caf38f042a80054d6c4280a8cc49e8f64a2eea59
2a3ff06a5521d749faeccd42b305a7278d7aa203b8c36f5a656ad1f420d11071
Both payments are on their chains and locked to the same secret hash 1ac9a92b6727678bf3710d3b80cb86e6497e7cbf, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 00bb2196ea83d87dbc01f710298020a5d9d26a11e4e9131e1ddf2126f88b449a
- TakerPaymentSent · TakerPaymentReceived: 2a3ff06a5521d749faeccd42b305a7278d7aa203b8c36f5a656ad1f420d11071
- TakerPaymentSpent: 08930a1d20287e81ed4edc7ebb2cf37547b7145d7ecc44880fcec5748bd55d4a
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.