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.
4671ced1594b2b900fe636435e859e89dd2b5f4a981ccbfc8d123661bf39315e
Both payments are on their chains and locked to the same secret hash b4e3d07ffdfbb9a4eac920060dc6b6b612df14a6, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 4671ced1594b2b900fe636435e859e89dd2b5f4a981ccbfc8d123661bf39315e
ec3516f809ccffe794f08ebe9a4208775e43e9635ca8c7d983950da18d79a7c9
Both payments are on their chains and locked to the same secret hash b4e3d07ffdfbb9a4eac920060dc6b6b612df14a6, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · b67da6d64650314b88f6d56bc7f4e83339969665241faa636c626be50077f616
- TakerPaymentReceived · ec3516f809ccffe794f08ebe9a4208775e43e9635ca8c7d983950da18d79a7c9
- TakerPaymentSpent · 1c8b7199684b6fe7b237af1f0be0372610cb7ee71b22322086c4b0d6292917de
No anomalies were recorded against this swap.
Reported by kdf-statsdb.