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.
8afb633883fc70840e3ae63433a33215c1266163b2bf507eba5c39f9ce085898
Both payments are on their chains and locked to the same secret hash 49a8769dcbe261ca4706690c60c77ab49deefc80, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 8afb633883fc70840e3ae63433a33215c1266163b2bf507eba5c39f9ce085898
- MakerPaymentSpent: c8bfcfdbcde1b65b23f7b64c414fa90177c8865b64185a91228ba73ca97dd977
81112b063ed3c306c2ce23b78ce5efac7ec8cf15c37f525d9eb572b1dadec65e
Both payments are on their chains and locked to the same secret hash 49a8769dcbe261ca4706690c60c77ab49deefc80, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 58cc559632220687dcfdc6fc2efabd4bcb6335bf52b3ce49f30af53f97269429
- TakerPaymentSent · TakerPaymentReceived: 81112b063ed3c306c2ce23b78ce5efac7ec8cf15c37f525d9eb572b1dadec65e
- TakerPaymentSpent: 1c24a04f70c59c4c3900cef2c5209e5648ff00cf5fa1c86bf3a152e06ac3c9d2
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.