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.
a61ffcd0770cb84de6bdc9d1eb0a2cd7421028878d362934acd1bdc9575a2084
Both payments are on their chains and locked to the same secret hash f3850898b6b1872aa5fdc1723fcc72540c9416e0, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: a61ffcd0770cb84de6bdc9d1eb0a2cd7421028878d362934acd1bdc9575a2084
- MakerPaymentSpent: 3119c138ba3bd6a44cb654368046a47c1ce1245cf98c9217a2e17750df44b66b
f5f7a65b96a07167fc92a8dfbac3ea6baa47d56b0a8f0d8b7ae30f6ca7dff9be
Both payments are on their chains and locked to the same secret hash f3850898b6b1872aa5fdc1723fcc72540c9416e0, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 9b69ee4208ccf09370a9cd009c483b03645a35f67e7aea218ea2e821d483f10a
- TakerPaymentSent · TakerPaymentReceived: f5f7a65b96a07167fc92a8dfbac3ea6baa47d56b0a8f0d8b7ae30f6ca7dff9be
- TakerPaymentSpent: 5901a4193901ba827710394cdbbff4688fb9da070efffde7a1e8a1cde0cf2f5e
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.