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.
31689e6e9dc9e2dbcdefc0acfc55dfaa59cfcb56debe04fcac6ffcecb84ec7fe
Both payments are on their chains and locked to the same secret hash bdd638cd1f770148b83cb76d263db62137a167f4, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 31689e6e9dc9e2dbcdefc0acfc55dfaa59cfcb56debe04fcac6ffcecb84ec7fe
- MakerPaymentSpent: ad38baf13b61fb6b6dab2b18db879e256fa8c8ca93d3fbe9460b73eea5b01495
695a6d77738ffe0ce855b06d770cd23d2dc3b0ebbb74226d54320ad3f925299c
Both payments are on their chains and locked to the same secret hash bdd638cd1f770148b83cb76d263db62137a167f4, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 935f1140f7cf2eb1f742ed32edacd7b1bbb4e8122751dcaaec710620ceda40a0
- TakerPaymentSent · TakerPaymentReceived: 695a6d77738ffe0ce855b06d770cd23d2dc3b0ebbb74226d54320ad3f925299c
- TakerPaymentSpent: 204b41cab0699645af00582802dae9f4e16ed35a1f80c36d805c0d630ef21929
Reported by kdf-statsdb.