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.
d29fbf25fcc6c7ff3ca5d2f68520c838979eae8166acc03a141ada7663e56e65
Both payments are on their chains and locked to the same secret hash ba10013fd5fa756398be5b5cf8dc9fe5be85f71e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: d29fbf25fcc6c7ff3ca5d2f68520c838979eae8166acc03a141ada7663e56e65
- MakerPaymentSpent: 5b92705f4890fe9f6dc5efeb8dd6b442f18ca9ab1d1fbd3799592057fcaecc0d
1869b67765917acb8d8e921dbdd280ce41578330f9546a47fa8b22e041597f61
Both payments are on their chains and locked to the same secret hash ba10013fd5fa756398be5b5cf8dc9fe5be85f71e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: f2e34085539540c18f30e3b5cd1e4f99ecb2a73a911fbb55fb72a415fbed05d4
- TakerPaymentSent · TakerPaymentReceived: 1869b67765917acb8d8e921dbdd280ce41578330f9546a47fa8b22e041597f61
- TakerPaymentSpent: c3d8c7c28e00b8135590378ac97295953c3180e7c56da127834fc61c795ebc96
Reported by kdf-statsdb-8762.