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.
f4c83a490fe1e5d04f9175d173a5fc6570e1ff16ea6bb8e20b91d71e4700d0c9
Both payments are on their chains and locked to the same secret hash 563f22d805bbdafd685565c2d73610879b929c1e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · f4c83a490fe1e5d04f9175d173a5fc6570e1ff16ea6bb8e20b91d71e4700d0c9
- MakerPaymentReceived · f4c83a490fe1e5d04f9175d173a5fc6570e1ff16ea6bb8e20b91d71e4700d0c9
- MakerPaymentSpent · 2365f3ded6a3fae8392ca59fb1a0b0592388933dd504df7038e57fad49e9d425
58446df75fc98483f09d227236bce8278d0bf55b804aa103fa30666ab42049f8
Both payments are on their chains and locked to the same secret hash 563f22d805bbdafd685565c2d73610879b929c1e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · 4fae8113c85994f3fdf15ab5108d88c1a35314bb95530f48b78f59ee3024d9da
- TakerPaymentReceived · 58446df75fc98483f09d227236bce8278d0bf55b804aa103fa30666ab42049f8
- TakerPaymentSpent · 11dee0d337c38cd570ff4f31fc9463037a2f76f41ec46301a7932c82c04eccb3
- TakerFeeSent · 4fae8113c85994f3fdf15ab5108d88c1a35314bb95530f48b78f59ee3024d9da
- TakerPaymentSent · 58446df75fc98483f09d227236bce8278d0bf55b804aa103fa30666ab42049f8
No anomalies were recorded against this swap.
Reported by kdf-statsdb-8762.