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.
ec1ea3a724c741bd777c85e31785699805c067bddb887fb1c36b5f96a0b5598d
Both payments are on their chains and locked to the same secret hash d2b0ab75498c16baf28273d4cd7bbac5a853d3bb, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · ec1ea3a724c741bd777c85e31785699805c067bddb887fb1c36b5f96a0b5598d
07335b27fbbc94dcdbb3e00aa29e3efe23a5d3c7f5e9862268b7f997c6349647
Both payments are on their chains and locked to the same secret hash d2b0ab75498c16baf28273d4cd7bbac5a853d3bb, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · 132f275e26437140b7c756a7df35d9431a631d78f8cef62c6614c0a2e8f4d930
- TakerPaymentReceived · 07335b27fbbc94dcdbb3e00aa29e3efe23a5d3c7f5e9862268b7f997c6349647
- TakerPaymentSpent · 6ed163ef9fc34cbc0b60627d823aab62b4b33df5d04dbb9847d54abaaae51825
No anomalies were recorded against this swap.
Reported by kdf-statsdb.