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.
b105b931132b7e5dd5dcd02ff646603b8eb388370b576bf66e55277ff19d896f
Both payments are on their chains and locked to the same secret hash 70e17ea172c9a31e15902c416dd423accbbc7f8b, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · b105b931132b7e5dd5dcd02ff646603b8eb388370b576bf66e55277ff19d896f
- MakerPaymentReceived · b105b931132b7e5dd5dcd02ff646603b8eb388370b576bf66e55277ff19d896f
- MakerPaymentSpent · 9c1d515a75daeabb99075574e9f794314b58a153aa583a6dc6e0f9d8e8ff1090
ff5ea395ae43acc80f79a8a0f3abad30f51e308c21b606998e3e749bd296a1d1
Both payments are on their chains and locked to the same secret hash 70e17ea172c9a31e15902c416dd423accbbc7f8b, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · 61646ed899a1f9164f4e21060f0df6429848186b87b2ebf9e7aa2739007ba1b5
- TakerPaymentReceived · ff5ea395ae43acc80f79a8a0f3abad30f51e308c21b606998e3e749bd296a1d1
- TakerPaymentSpent · dc6e79acae87c48c7faa68a0bfaa01ca8c90f03c2856ed6de96f05e4090e3e48
- TakerFeeSent · 61646ed899a1f9164f4e21060f0df6429848186b87b2ebf9e7aa2739007ba1b5
- TakerPaymentSent · ff5ea395ae43acc80f79a8a0f3abad30f51e308c21b606998e3e749bd296a1d1
No anomalies were recorded against this swap.
Reported by kdf-statsdb-8762.