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.
a4fc321f861f4bca1549e27b6aa317e44d846ca7404f00f71fb0649759d63e2b
Both payments are on their chains and locked to the same secret hash 6fd81a66d24be3cfefb879b3b7654951cbdde888, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · a4fc321f861f4bca1549e27b6aa317e44d846ca7404f00f71fb0649759d63e2b
7942fe84a48e8629876d0808c53f4de720c3295b41dd57e81b62c9a0eff79307
Both payments are on their chains and locked to the same secret hash 6fd81a66d24be3cfefb879b3b7654951cbdde888, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · de9cb4c750bc369eb918758d1a5c736a99e690abe08d0913e9959a4819cf34ec
- TakerPaymentReceived · 7942fe84a48e8629876d0808c53f4de720c3295b41dd57e81b62c9a0eff79307
- TakerPaymentSpent · 95b4f139e794f97f84d22cb79244c7f4e19efbe623ea1248e867b9419e583d11
No anomalies were recorded against this swap.
Reported by kdf-statsdb.