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.
008484071d0f53499de0184b12a36d891a1e39c09963190b20b4b519ebcaad1e
Both payments are on their chains and locked to the same secret hash 1992658b366c8f438f470eddbadc5c8fde14ab9f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 008484071d0f53499de0184b12a36d891a1e39c09963190b20b4b519ebcaad1e
- MakerPaymentSpent: a966fe21d49cceb497299e80af88e36a89316725d4ea0684c504d55b0273d3ef
b17e68f92cfb185ab44674e0441dac33292381758297dbedfdb2ab2361da81b2
Both payments are on their chains and locked to the same secret hash 1992658b366c8f438f470eddbadc5c8fde14ab9f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 985afad6948b06012e90b5deb9526f51cad7687d36018d8e640a00c45e873a13
- TakerPaymentSent · TakerPaymentReceived: b17e68f92cfb185ab44674e0441dac33292381758297dbedfdb2ab2361da81b2
- TakerPaymentSpent: 511577d3eaff174e3e5c93628612741cc445f886f7b0cc5bcf33e75c4aab7340
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.