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.
69b19c3160363dd58bcbd1f171da88b56386ba6311f5fc7fb01b2b606b7a3848
Both payments are on their chains and locked to the same secret hash 7804d6b354d5380a04328cc29d6f50cb6f4e0073, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 69b19c3160363dd58bcbd1f171da88b56386ba6311f5fc7fb01b2b606b7a3848
1ef4f73ec452748b1f29f7b7ba4309f80841242e813b9164adea8e021947ee03
Both payments are on their chains and locked to the same secret hash 7804d6b354d5380a04328cc29d6f50cb6f4e0073, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: a381694bad92a33803f11fe9509cb7e8a0173f455a6480a17ade829034f0a150
- TakerPaymentReceived: 1ef4f73ec452748b1f29f7b7ba4309f80841242e813b9164adea8e021947ee03
- TakerPaymentSpent: b4adcf3e347f754ffa1c7900b1292cc91f368583c1e5f3cc5731d85033f2c769
Reported by kdf-statsdb.