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.
38ddede8ebc5934d8de4346070f8cd84f7a7cf7096ac1255bd80cc020a76e3a0
Both payments are on their chains and locked to the same secret hash 4f7b46fa2729589d73c53f6f4a1a25cf3678fb99, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 38ddede8ebc5934d8de4346070f8cd84f7a7cf7096ac1255bd80cc020a76e3a0
- MakerPaymentSpent: 920814e4c82dfcb74db8c74ba422c586eaf60b0ca422e50b0d543310adc98b89
2242e2d7581f7f71f0b08f2cf713dbf05497e97946e99acbb56531aff20614e4
Both payments are on their chains and locked to the same secret hash 4f7b46fa2729589d73c53f6f4a1a25cf3678fb99, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: ab29dcaabba30a92dfc7cf8eb8b48bb69118d8107d92ff8028e93d7d57909864
- TakerPaymentSent · TakerPaymentReceived: 2242e2d7581f7f71f0b08f2cf713dbf05497e97946e99acbb56531aff20614e4
- TakerPaymentSpent: 1b637eb483665639e5491018d9ed75ff91ebbb78b4cae0ff52372889aa8eb2f2
Reported by kdf-statsdb.