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.
633e643315045390a5323a5ea10c7e6629de4c0958ad5fa93c657c9c34a01acc
Both payments are on their chains and locked to the same secret hash 7648ce0d71f11b272218e95c9a0cab0148a18865, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 633e643315045390a5323a5ea10c7e6629de4c0958ad5fa93c657c9c34a01acc
- MakerPaymentSpent: 604422858ea417567abb0126b38c71057a6639dc9942961add7438c2c7bf8dda
b80e0a38ff97bbaee99aba2af73aae0aad4f607c2b4545aa77846887ffd95fbf
Both payments are on their chains and locked to the same secret hash 7648ce0d71f11b272218e95c9a0cab0148a18865, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 189d434ff1314b6e2d7d96305c32929998796deed425cf4ff069a9616384ac42
- TakerPaymentSent · TakerPaymentReceived: b80e0a38ff97bbaee99aba2af73aae0aad4f607c2b4545aa77846887ffd95fbf
- TakerPaymentSpent: 65960bb46fee2552990892aa26d9d899b4d0a20d1846250a9422af8196a75da8
Reported by kdf-statsdb.