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.
d80788ebac22c695695afb96752b65f17c9f176e5939612f6b2aecca6f4928ec
Both payments are on their chains and locked to the same secret hash 1bb4dcf866354e5158da6c972f0bf4992a2b8089, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: d80788ebac22c695695afb96752b65f17c9f176e5939612f6b2aecca6f4928ec
- MakerPaymentSpent: 53188ca529296b961761539cb383a6c9ad1aaf12a1f2d22f146cad74cf83a2e9
aaca8dd63b76e71734c9818310dbd4ccf001d50ef85c464ebae85f3a28608043
Both payments are on their chains and locked to the same secret hash 1bb4dcf866354e5158da6c972f0bf4992a2b8089, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 48edf4b7d9901c77af38adc310b12326a2940f1e85c2bca416ffbf35d0ddd250
- TakerPaymentSent · TakerPaymentReceived: aaca8dd63b76e71734c9818310dbd4ccf001d50ef85c464ebae85f3a28608043
- TakerPaymentSpent: 37e10e1462380044ff2f0c975e880bc0aa13e1fabda774c2ea112104ed7571a4
Reported by kdf-statsdb-8762.