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.
4894771e3bf95d245a532573fdc21db7bcdac8025f7cc350d42e15d816cfd457
Both payments are on their chains and locked to the same secret hash 7d6611aaf19ebc2640ff72f518c26956523ac285, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 4894771e3bf95d245a532573fdc21db7bcdac8025f7cc350d42e15d816cfd457
- MakerPaymentSpent: 79977700a374c42d65c2cbf217b809c5e939e0e8ffbb05a763e9d93b99784b5b
2c4fdb39a26ee2039b7c7245110e3136ecc263622958acf0a7ab147064560722
Both payments are on their chains and locked to the same secret hash 7d6611aaf19ebc2640ff72f518c26956523ac285, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: b0c304204b1a5913fdc64f08ebbf42735572aa3ac623d7793161944fb6edf624
- TakerPaymentSent · TakerPaymentReceived: 2c4fdb39a26ee2039b7c7245110e3136ecc263622958acf0a7ab147064560722
- TakerPaymentSpent: 8aec787868af8c2f9e580fadb3541fe464c19021b171629484b0ebf1d0ce3a0e
Reported by kdf-statsdb-8762.