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.
94da5a51663ace84d69c966e505c0a32f9e264aeef36a7d6cef351b57e57befe
Both payments are on their chains and locked to the same secret hash 65ca651c8554a77ac0e9bfb319e695ebac0c6f1b, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 94da5a51663ace84d69c966e505c0a32f9e264aeef36a7d6cef351b57e57befe
- MakerPaymentReceived · 94da5a51663ace84d69c966e505c0a32f9e264aeef36a7d6cef351b57e57befe
- MakerPaymentSpent · e5c6a630bdcf21aebe1f2335afc24c58f6f3381b16e228976a279e1f9dce63cd
f49bd91ca427ade4f969939b5665295f4f702bb4361bdc151019ef4e05fe0bf3
Both payments are on their chains and locked to the same secret hash 65ca651c8554a77ac0e9bfb319e695ebac0c6f1b, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · d467e438af8da94a995186de77091a574e005561f9181cd9c8a7b0e1a6c275a9
- TakerPaymentReceived · f49bd91ca427ade4f969939b5665295f4f702bb4361bdc151019ef4e05fe0bf3
- TakerPaymentSpent · eb624d79b868b86621b77dd1552d1c830217a254b343f83e45dd7942f0562510
- TakerFeeSent · d467e438af8da94a995186de77091a574e005561f9181cd9c8a7b0e1a6c275a9
- TakerPaymentSent · f49bd91ca427ade4f969939b5665295f4f702bb4361bdc151019ef4e05fe0bf3
No anomalies were recorded against this swap.
Reported by kdf-statsdb-8762.