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.
dad6e35548416bec8add9f4aa97c1da8a462ac4e89132916c989ff4dea7b3e7b
Both payments are on their chains and locked to the same secret hash 6b6f5873dff78ec58588683b115549732cfc5e72, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · dad6e35548416bec8add9f4aa97c1da8a462ac4e89132916c989ff4dea7b3e7b
9b08454222e1d10104c6e9973d8f82cf576b77e8bcd4ddc22051a0df6f8c887e
Both payments are on their chains and locked to the same secret hash 6b6f5873dff78ec58588683b115549732cfc5e72, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · ebd64cc474045778f0ed952f2c5a8cb1fdf26e11bc9bea466f5a09bf775e1908
- TakerPaymentReceived · 9b08454222e1d10104c6e9973d8f82cf576b77e8bcd4ddc22051a0df6f8c887e
- TakerPaymentSpent · 69d5fa5484f28456411563d928fdd114ed287031da092d75312b2a00262cefbd
No anomalies were recorded against this swap.
Reported by kdf-statsdb-8762.