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.
bfb970f4338fb764676696d56525aed12a756d073d62160cfeeca8f8161eefba
Both payments are on their chains and locked to the same secret hash a8ff191d9189ca753a4bba37a12a00faf226afd2, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: bfb970f4338fb764676696d56525aed12a756d073d62160cfeeca8f8161eefba
- MakerPaymentSpent: b269b7513b751a51cd86adb3005100135191b327773e1f6075916245e7c53ebf
f8a8fa6505219c92b9c501f1615d7a00d61013bae8c16c114a30a3e41c05b697
Both payments are on their chains and locked to the same secret hash a8ff191d9189ca753a4bba37a12a00faf226afd2, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 3af8344f37367923fc5524190bde115247b2e9f864ad5c4b1bb69ebb1b9113be
- TakerPaymentSent · TakerPaymentReceived: f8a8fa6505219c92b9c501f1615d7a00d61013bae8c16c114a30a3e41c05b697
- TakerPaymentSpent: b792d42758ad411fa516675fdbfec955f75220644eb2b4adc53a863e81a81462
Reported by kdf-statsdb-8762.