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.
11f3643b0911ac1f02bb78fd343f440e2e460b711eacdda232185af4ebe00a25
Both payments are on their chains and locked to the same secret hash f07d9a121681aa25ab1e58506a661d11c40115f1, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 11f3643b0911ac1f02bb78fd343f440e2e460b711eacdda232185af4ebe00a25
- MakerPaymentSpent: 8f28cbcc684be96e1e585f6772b2f4482dbb701823d7653e76768b2c7d8de93c
54fe6f56044438065aeea0c349f98f21cccdaf9637a0370d8ae4eb916349a00d
Both payments are on their chains and locked to the same secret hash f07d9a121681aa25ab1e58506a661d11c40115f1, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: 2879d21979628dafb50ad011c2054488b0598f89892936903a1abedc75dbf9b3
- TakerPaymentSent · TakerPaymentReceived: 54fe6f56044438065aeea0c349f98f21cccdaf9637a0370d8ae4eb916349a00d
- TakerPaymentSpent: 188f67252e5a60e4203e9d2012d4f0b180da216b508e11dac07c97a46cf75e39
Reported by kdf-statsdb.