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.
9635d8fa02256aa95b1f8617215a6af7638b55fe867bb4f0f01e7ee0d7d988e1
Both payments are on their chains and locked to the same secret hash 39fd642f231986258874afc025ff9e37417d200b, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 9635d8fa02256aa95b1f8617215a6af7638b55fe867bb4f0f01e7ee0d7d988e1
- MakerPaymentSpent: 9ecf0d9ffb694b6bd202acf314e49012d6bf51e0a3867700f52644d97ea435c8
d777e3a0996d6b4ebfe27017f90ae2c0f4ca4eb716e8607b26fbf300dd932407
Both payments are on their chains and locked to the same secret hash 39fd642f231986258874afc025ff9e37417d200b, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 8630dac3a53a5586bf244e1ad949dc3fc112aa0bdf38f3a667ae7cefbadf82c0
- TakerPaymentSent · TakerPaymentReceived: d777e3a0996d6b4ebfe27017f90ae2c0f4ca4eb716e8607b26fbf300dd932407
- TakerPaymentSpent: ed6e4502a25e732b24685f31ec049ab6f4eb3b4006e0a91ce329c48a5cb77d01
Reported by kdf-statsdb.