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.
46aaadb04b1509db61084dc1929aad19c9d81ae90a9c360b3f91368a360d2d4f
Both payments are on their chains and locked to the same secret hash 0552c29ad33fd22a04e7c0b16ba655e39818bc91, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 46aaadb04b1509db61084dc1929aad19c9d81ae90a9c360b3f91368a360d2d4f
- MakerPaymentReceived · 46aaadb04b1509db61084dc1929aad19c9d81ae90a9c360b3f91368a360d2d4f
- MakerPaymentSpent · f76392d2bbc69765220d6c0974df5ae91ff4bfc1ea396aa8fa4531a073f3011c
1573460e9e2181104351d9fc5d9cc6b723f59eed016178aad00446d3e70ed447
Both payments are on their chains and locked to the same secret hash 0552c29ad33fd22a04e7c0b16ba655e39818bc91, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · f37d0c0febaf8b114a41f7e566eb6f861ad3f30277fcd72d615cda126a4e08b9
- TakerPaymentReceived · 1573460e9e2181104351d9fc5d9cc6b723f59eed016178aad00446d3e70ed447
- TakerPaymentSpent · 4f49bc72f037811c6f091520d3bda26c5291a2bfcd5c6fbed317045545950f81
- TakerFeeSent · f37d0c0febaf8b114a41f7e566eb6f861ad3f30277fcd72d615cda126a4e08b9
- TakerPaymentSent · 1573460e9e2181104351d9fc5d9cc6b723f59eed016178aad00446d3e70ed447
No anomalies were recorded against this swap.
Reported by kdf-statsdb-8762.