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.
7ca24ec31d7f1d5638e03cfbf98d1ad139fdfdff0033ca48a5be3e982bc45b28
Both payments are on their chains and locked to the same secret hash 3bdd0dcd8b02827d847c3ae3d05b7accba0d156e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 7ca24ec31d7f1d5638e03cfbf98d1ad139fdfdff0033ca48a5be3e982bc45b28
- MakerPaymentSpent: d41874f43387a5695aad6591f92aaddba2b08e0d0cdb8bf4b422acecb220664a
9ffa5fd245eed150098ce80ea998744fe731a1a0a9824f370eb76858371ab6a2
Both payments are on their chains and locked to the same secret hash 3bdd0dcd8b02827d847c3ae3d05b7accba0d156e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: fdeacf0ba6cfbf193d838dd916b7735468160ee9e076f742fe08bac53518a560
- TakerPaymentSent · TakerPaymentReceived: 9ffa5fd245eed150098ce80ea998744fe731a1a0a9824f370eb76858371ab6a2
- TakerPaymentSpent: 5fce2da228d39ac8e1ada8919a6f39b14dd6559effda5856e599d879e613e661
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.