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.
04f7ebb92ef8d2c6c18c2bd33c90d2016c4a5cf1553729118738ecd36327a102
Both payments are on their chains and locked to the same secret hash 02e65bebce163fbeb61a1c72cd82e37ef7272ee5, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 04f7ebb92ef8d2c6c18c2bd33c90d2016c4a5cf1553729118738ecd36327a102
- MakerPaymentReceived · 04f7ebb92ef8d2c6c18c2bd33c90d2016c4a5cf1553729118738ecd36327a102
- MakerPaymentSpent · 84101a3428bbace18a3ef8e359fa844a21d82505c2955353a8f5ef24197d354d
1cb01c367f669ec3a320149fa0e959e85a0d8518b12ee0fd22dd4730ec311c95
Both payments are on their chains and locked to the same secret hash 02e65bebce163fbeb61a1c72cd82e37ef7272ee5, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · 6d3b3d0a50d44fbc9e8b5e730b8b3b53725c6dd82caf12ac45d73a21fa44a504
- TakerPaymentReceived · 1cb01c367f669ec3a320149fa0e959e85a0d8518b12ee0fd22dd4730ec311c95
- TakerPaymentSpent · b1b8fc2ad0e9171f2fde9ab667dc1648a883f7eff2d4add6a01ba932745db913
- TakerFeeSent · 6d3b3d0a50d44fbc9e8b5e730b8b3b53725c6dd82caf12ac45d73a21fa44a504
- TakerPaymentSent · 1cb01c367f669ec3a320149fa0e959e85a0d8518b12ee0fd22dd4730ec311c95
No anomalies were recorded against this swap.
Reported by kdf-statsdb-8762.