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.
a9ec3c73e0cd4a1fefff83b091d7781cca2ca1fda466ed4973501c4c7725c663
Both payments are on their chains and locked to the same secret hash ac2528def75277b2911882f1f45df551e2a18237, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · a9ec3c73e0cd4a1fefff83b091d7781cca2ca1fda466ed4973501c4c7725c663
e95153b6bcc2e524df7019a6810ad10b6917f246adb63c1448be7ed5c6dc7dd6
Both payments are on their chains and locked to the same secret hash ac2528def75277b2911882f1f45df551e2a18237, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · 2d062d399815ed4610ab22bcffd3eae6956e0307de1d3daa6f9857d166d4afa3
- TakerPaymentReceived · e95153b6bcc2e524df7019a6810ad10b6917f246adb63c1448be7ed5c6dc7dd6
- TakerPaymentSpent · 1e0d80dc4c3a8953e825132a5fc8f55f46591585dc8f7427da5018263eb405f7
No anomalies were recorded against this swap.
Reported by kdf-statsdb-8762.