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.
29c4b5a8241bd27453b4de50ef219f972ac4e47600d118cf280d4b147682772e
Both payments are on their chains and locked to the same secret hash 82deed0aff8e3066a19db2fa14e77a84097c1326, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 29c4b5a8241bd27453b4de50ef219f972ac4e47600d118cf280d4b147682772e
b0c096a9076d11be5f7f8b2613d48d8d3ce474f3bb657529bb38a19313ec43a5
Both payments are on their chains and locked to the same secret hash 82deed0aff8e3066a19db2fa14e77a84097c1326, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · b71ee427defa97377bf4e3140295f3372f4201efc9ff7af91613d068b45a9881
- TakerPaymentReceived · b0c096a9076d11be5f7f8b2613d48d8d3ce474f3bb657529bb38a19313ec43a5
- TakerPaymentSpent · 9ef773a88bb961def612dae4845f5e821dc0f266635b36dfb61856cf3d8d3ec6
Reported by kdf-statsdb.