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.
da7966df6757533bcc0c54c812b86d2e9648aedac3e7cd69e40010a97943e149
Both payments are on their chains and locked to the same secret hash 8bb5971b100e83953e6320c07d720e28d2c39dfd, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · da7966df6757533bcc0c54c812b86d2e9648aedac3e7cd69e40010a97943e149
7be4dc3a47601cdb4c2ed22f881be4e47bcf2c8cc453e4d5c8457de01751a87f
Both payments are on their chains and locked to the same secret hash 8bb5971b100e83953e6320c07d720e28d2c39dfd, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · 99888bcb9cf7958fae2c1eb7f8ea19028007b7acbf49721afd4e805a39c2311a
- TakerPaymentReceived · 7be4dc3a47601cdb4c2ed22f881be4e47bcf2c8cc453e4d5c8457de01751a87f
- TakerPaymentSpent · 2f2c5a5e6ddaf3372ff9d36173549dbebfc60f68bc15e4737f2c54cea2bc3483
No anomalies were recorded against this swap.
Reported by kdf-statsdb.