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.
0d07aefe2c9e4819aac4a30a6e7e33c0c1aa14c5d4aba495a3937b1434bef404
Both payments are on their chains and locked to the same secret hash 7a6adc24d9893ce3a7762f13d1dee0816db7b245, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 0d07aefe2c9e4819aac4a30a6e7e33c0c1aa14c5d4aba495a3937b1434bef404
- MakerPaymentSpent: b542e6b05519668cc72ff3a0f47638e1370d613a3ac395d6b9d456f634de4388
b53a27ad7f89b27aa1aceb4b6be0b215880b1cf07438761548f6f47c55adeb95
Both payments are on their chains and locked to the same secret hash 7a6adc24d9893ce3a7762f13d1dee0816db7b245, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 24c8a725b723bee5896fe4e3bced207ad677e82b247aa6c3c3eb938210e6e5d4
- TakerPaymentSent · TakerPaymentReceived: b53a27ad7f89b27aa1aceb4b6be0b215880b1cf07438761548f6f47c55adeb95
- TakerPaymentSpent: f566aaa6942510366ddb2869dccc3c3a0ffeb9ceb5730b863a4d644ab9e70d26
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.