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.
8f189ac74f86f66d4f4b1c350c2fe1599923cfb1e194d9d76097eeac9ea2303b
Both payments are on their chains and locked to the same secret hash 74c8dee123f0ff8ae73962a8ef82425381fcc72d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 8f189ac74f86f66d4f4b1c350c2fe1599923cfb1e194d9d76097eeac9ea2303b
960a5b34d51d3431a273790d7e57b64549f60985539cdae8f6a07dce91cbac0b
Both payments are on their chains and locked to the same secret hash 74c8dee123f0ff8ae73962a8ef82425381fcc72d, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · d94dfac51a8a5bd82b9546c19448c7f00aee312de3a2639a8c257187e3aff065
- TakerPaymentReceived · 960a5b34d51d3431a273790d7e57b64549f60985539cdae8f6a07dce91cbac0b
- TakerPaymentSpent · 034fcd6f406f490c798061b603094c55fc34279d5b52de5e30d3358f5e7c0e12
No anomalies were recorded against this swap.
Reported by kdf-statsdb.