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.
320fafe0c1307be31025da091aecbcc69c8796b4fbd59cbb29b43164a157f8cd
Both payments are on their chains and locked to the same secret hash 465da131940d116d90d0f02a14011c282ccff0c0, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 320fafe0c1307be31025da091aecbcc69c8796b4fbd59cbb29b43164a157f8cd
- MakerPaymentSpent: 6b835fc89fdf338c96053dfec588e9fe700afe96b0d61b05966e7ad87f21c7e3
3d0f3a1d1111e52696db4faeac23364158567dc861155a563fe07e2dd6f359ee
Both payments are on their chains and locked to the same secret hash 465da131940d116d90d0f02a14011c282ccff0c0, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: c01d8bbf63ba5d8a5b90ae49ed630f34a9d96014f4b5ccda5b0c4cf9194afb04
- TakerPaymentSent · TakerPaymentReceived: 3d0f3a1d1111e52696db4faeac23364158567dc861155a563fe07e2dd6f359ee
- TakerPaymentSpent: 5865f276ed1d65d413a95c9695884d814adb21d2b96f0942df7da970d6168d7f
Reported by kdf-statsdb-8762.