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.
ce4d0d7d7ffe066c54b3a6b6b6a38cead599126d85b64e744a3ba8ae3174a6eb
Both payments are on their chains and locked to the same secret hash a1d68b1ac61dd650ffc43b294cc5c79f7f3b3eb5, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · ce4d0d7d7ffe066c54b3a6b6b6a38cead599126d85b64e744a3ba8ae3174a6eb
- MakerPaymentReceived · ce4d0d7d7ffe066c54b3a6b6b6a38cead599126d85b64e744a3ba8ae3174a6eb
- MakerPaymentSpent · 416691efa30bcb3b589a36f90857f1377c5a7bf17471f120d5c1f21f33144621
2a2f5eb3a8c261c93fe45fe6d6fdccda59c23f4fd7d280426d22b36a176ad3e5
Both payments are on their chains and locked to the same secret hash a1d68b1ac61dd650ffc43b294cc5c79f7f3b3eb5, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · 90f7b229b958cc9a91ee09a807078f6c540f4e6068fa5553d0c27406e481ce39
- TakerPaymentReceived · 2a2f5eb3a8c261c93fe45fe6d6fdccda59c23f4fd7d280426d22b36a176ad3e5
- TakerPaymentSpent · a6100696964d980bcdb06ccd96ef27fc708b876b72540bf7b71846ac43424161
- TakerFeeSent · 90f7b229b958cc9a91ee09a807078f6c540f4e6068fa5553d0c27406e481ce39
- TakerPaymentSent · 2a2f5eb3a8c261c93fe45fe6d6fdccda59c23f4fd7d280426d22b36a176ad3e5
No anomalies were recorded against this swap.
Reported by kdf-statsdb-8762.