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.
e23655d6118fea9a0441efe571743e83d5f0eda1fb7de9697799de49947fae40
Both payments are on their chains and locked to the same secret hash 5f2a5576af6c51e6bee88115edd0e9ab2e1b0622, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: e23655d6118fea9a0441efe571743e83d5f0eda1fb7de9697799de49947fae40
- MakerPaymentSpent: c51afc58ec37471c7a9dd1330bfad22223febb2c658d4699235ac98cc7d15fed
cc0fff24a9277b84dd216f1ea74cd83fa4569380aff2817202c3067a67fb0962
Both payments are on their chains and locked to the same secret hash 5f2a5576af6c51e6bee88115edd0e9ab2e1b0622, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: e109a7bed3b81e72098ffbff11e0b35571c4cbcff1d4a2526e48c6f5c9a0ee5f
- TakerPaymentSent · TakerPaymentReceived: cc0fff24a9277b84dd216f1ea74cd83fa4569380aff2817202c3067a67fb0962
- TakerPaymentSpent: 6e776eaf98c34bbcd87dcbb523ae4d70870e69b39f107eef91e364a2b67c318e
Reported by kdf-statsdb-8762.