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.
0c4aa299bde9e40520408b78eff825308c69489244f50ceedc6bc22b0edf2b94
Both payments are on their chains and locked to the same secret hash 8d437a51eb376000473344bdea67b99f5da5e970, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 0c4aa299bde9e40520408b78eff825308c69489244f50ceedc6bc22b0edf2b94
- MakerPaymentReceived · 0c4aa299bde9e40520408b78eff825308c69489244f50ceedc6bc22b0edf2b94
- MakerPaymentSpent · c63a71ec0f967dea9f6737633621148f5ccd172d725c30ae9193b4a3e7ebf347
1cd434b2f3f95377e32ffefc8c63ca38fdb7341d3007426b18974ab23c4be322
Both payments are on their chains and locked to the same secret hash 8d437a51eb376000473344bdea67b99f5da5e970, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · 80bb6d225d791fbd0f71314cdf91c514e2e1c92615a4510e9d068be61b33c411
- TakerPaymentReceived · 1cd434b2f3f95377e32ffefc8c63ca38fdb7341d3007426b18974ab23c4be322
- TakerPaymentSpent · 49a4536b13eac10a6dba9a21489c52ed56dca241b9311702ee39b7b5c02b7d01
- TakerFeeSent · 80bb6d225d791fbd0f71314cdf91c514e2e1c92615a4510e9d068be61b33c411
- TakerPaymentSent · 1cd434b2f3f95377e32ffefc8c63ca38fdb7341d3007426b18974ab23c4be322
No anomalies were recorded against this swap.
Reported by kdf-statsdb-8762.