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.
c17c430f8754447ae85f6179fdb654ba0ce5750031c391c65c5111ee01a6b875
Both payments are on their chains and locked to the same secret hash 91852b500e88c0d20f9f1e24a8280ff72f87b80e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: c17c430f8754447ae85f6179fdb654ba0ce5750031c391c65c5111ee01a6b875
- MakerPaymentSpent: 91dfbf0a52e4bd63d4905ddd0509bbec844b07ac83b85ff52d7315caa23669de
f79c47623ff28e1939447a97a46dea691e3266d5fcb80ef96a5c5443f81abff4
Both payments are on their chains and locked to the same secret hash 91852b500e88c0d20f9f1e24a8280ff72f87b80e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 4b2396557290a53e6ca28e405ce0d887f779c95126f4f3eb0275475fe8326630
- TakerPaymentSent · TakerPaymentReceived: f79c47623ff28e1939447a97a46dea691e3266d5fcb80ef96a5c5443f81abff4
- TakerPaymentSpent: 77ca845e5c094de893c928a8cec611dcf77d8614bcf2a52703f9743ab921b610
Reported by kdf-statsdb.