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.
4d1075c9b9694ed212f84b5809ed27b8821ff24ea2509e0de0d61f5693ebbb14
Both payments are on their chains and locked to the same secret hash 37e92a2f4b419863ba1ab34723bbc54f0a2af545, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 4d1075c9b9694ed212f84b5809ed27b8821ff24ea2509e0de0d61f5693ebbb14
- MakerPaymentReceived · 4d1075c9b9694ed212f84b5809ed27b8821ff24ea2509e0de0d61f5693ebbb14
- MakerPaymentSpent · 2c4becc79f2805aeea24cc9eabd5fc11e3e71f3696ec2551a2a5d63955c99525
51f667c6f2bd78e0df0ff6103cd857b72e8297922213229b630f087904d9a209
Both payments are on their chains and locked to the same secret hash 37e92a2f4b419863ba1ab34723bbc54f0a2af545, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · 866b8da425b851bbea926aed49c22865ebbca5c53daae7b7aa57c14e30274824
- TakerPaymentReceived · 51f667c6f2bd78e0df0ff6103cd857b72e8297922213229b630f087904d9a209
- TakerPaymentSpent · 29fcf51344d1721e8e538533feae6575b549e7a2bb024593aaf9cffd5c384493
- TakerFeeSent · 866b8da425b851bbea926aed49c22865ebbca5c53daae7b7aa57c14e30274824
- TakerPaymentSent · 51f667c6f2bd78e0df0ff6103cd857b72e8297922213229b630f087904d9a209
No anomalies were recorded against this swap.
Reported by kdf-statsdb-8762.