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.
39499a6858810fcc958583b9379072b7d76cb87886864c1521b6f0a262b1b435
Both payments are on their chains and locked to the same secret hash 53f61271c61cd33df0a5a5c0cbec2029ccbae06d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 39499a6858810fcc958583b9379072b7d76cb87886864c1521b6f0a262b1b435
8dd972feda8f9363524256052e2fc4aca77ff51cf06ced6c63aa23a810f266f9
Both payments are on their chains and locked to the same secret hash 53f61271c61cd33df0a5a5c0cbec2029ccbae06d, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · 14033fd97cdbf634cc87172d7dbfece6c3bc4edef0d60360416bddb49f42e368
- TakerPaymentReceived · 8dd972feda8f9363524256052e2fc4aca77ff51cf06ced6c63aa23a810f266f9
- TakerPaymentSpent · b4cd666a796ec67126fec96f6835873926506736a0d69d8e1ee1895119cd15a1
No anomalies were recorded against this swap.
Reported by kdf-statsdb-8762.