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.
32051c0a722c6b2d8cb9d040804d0466f1aa215f0ab894530a4ddbe7f5490ab8
Both payments are on their chains and locked to the same secret hash aad56839e0905818af946211bf49f4324cb225c1, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 32051c0a722c6b2d8cb9d040804d0466f1aa215f0ab894530a4ddbe7f5490ab8
- MakerPaymentSpent: 19e8bcfc01e8db1d027e17ecaf7a6299bfda1e657d76bd11368c693be411088a
6553e25f5a5ea91a06d999af6db5ba550e297bad500fe76a9bf0d01808d55bf5
Both payments are on their chains and locked to the same secret hash aad56839e0905818af946211bf49f4324cb225c1, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: e346908cc67e4d0c61a1ce15bde0c1dcce98d811cafc172c7c4f1877092a4335
- TakerPaymentSent · TakerPaymentReceived: 6553e25f5a5ea91a06d999af6db5ba550e297bad500fe76a9bf0d01808d55bf5
- TakerPaymentSpent: 15b348a1828270d256dcf9b3f6be507665070db4c6fbd7eb1a72232b1eb10ed3
Reported by kdf-statsdb-8762.