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.
4dcbab4bde0edf48e3b92bd33416201f956e1c4696410753aff9d38c87eedfad
Both payments are on their chains and locked to the same secret hash 0966afb86b788257d7a0e9c6645d766a95fbf9df, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 4dcbab4bde0edf48e3b92bd33416201f956e1c4696410753aff9d38c87eedfad
912cc9fb6d9734229bb9c7278d09bbaddb9517977b60419b1fea1257d94d3d30
Both payments are on their chains and locked to the same secret hash 0966afb86b788257d7a0e9c6645d766a95fbf9df, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · b700bc7b76cb672f3830a715f5dba96c8e2197b22445759dfc158b4662d6a594
- TakerPaymentReceived · 912cc9fb6d9734229bb9c7278d09bbaddb9517977b60419b1fea1257d94d3d30
- TakerPaymentSpent · ced76aa6b3bba54a2c14f44ccc51a19c6c7a5a2729ff6cf8f752b5ad97b77da9
No anomalies were recorded against this swap.
Reported by kdf-statsdb.