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.
852cdf4955595d428d70dc0d465c16d41222c1006e8c7e7623e198d25f861c7a
Both payments are on their chains and locked to the same secret hash 15048ab7bdfabc5ad5ee69d58535fbae97df7a5a, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 852cdf4955595d428d70dc0d465c16d41222c1006e8c7e7623e198d25f861c7a
- MakerPaymentSpent: 15115f857a84c03e62b98563fde13c45c7f463f8e9aded22079a579bbe4db90f
a9036e091c3458f1aca56f977c1b62f9ea2a5fe72495439a2e0acb96d755a148
Both payments are on their chains and locked to the same secret hash 15048ab7bdfabc5ad5ee69d58535fbae97df7a5a, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 066cee46a764561dfdd06587a9be12711ec5d74ced893f78feef4b04172bfb37
- TakerPaymentSent · TakerPaymentReceived: a9036e091c3458f1aca56f977c1b62f9ea2a5fe72495439a2e0acb96d755a148
- TakerPaymentSpent: 4e2de5c3c0e9ffecf7232e0133c1217b71055b8bb631b17df7455c2d1432a7c3
Reported by kdf-statsdb.