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.
de56a6621d109543ce5ed3539bcfcba872b13b8ce03e7eaf9da75c5aba57c00c
Both payments are on their chains and locked to the same secret hash a4719e624f64d35d56230887fae85d39d075f156, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived: de56a6621d109543ce5ed3539bcfcba872b13b8ce03e7eaf9da75c5aba57c00c
- MakerPaymentSpent: 9a67ca8a1ff452c4a4d904ad92e00776088dc36260648803833b4237ca3637a2
56040fa1c1e74795b261f7acacdb1340ff6d38b9686397e5e619e8d9597692a1
Both payments are on their chains and locked to the same secret hash a4719e624f64d35d56230887fae85d39d075f156, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent: d3c5218c42b5f50da5e99a10b97d18bc11c9fcaaa623fdf80c4a5e7eedc66189
- TakerPaymentSent: 56040fa1c1e74795b261f7acacdb1340ff6d38b9686397e5e619e8d9597692a1
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.