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.
8e92fa9715ee374c12a3fa2cf4e15b6734975a76f79ec7d171c614173cd26110
Both payments are on their chains and locked to the same secret hash 468e0da84b06989d2bda7671f86797050f52b892, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 8e92fa9715ee374c12a3fa2cf4e15b6734975a76f79ec7d171c614173cd26110
- MakerPaymentSpent: fce287e69fc7c84ae0f7f9d4ffd50ec2140891a22e5a364566cd68ebc2cedc61
efad86e62c9da71ca1a1dd6761adecbfa8fbd2344efcc33221ca7581b549dd6d
Both payments are on their chains and locked to the same secret hash 468e0da84b06989d2bda7671f86797050f52b892, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: f1a9d57421fc6344940f71dd00b5c7e20705d526adcf9421b893811f3a01b0d0
- TakerPaymentReceived · TakerPaymentSent: efad86e62c9da71ca1a1dd6761adecbfa8fbd2344efcc33221ca7581b549dd6d
- TakerPaymentSpent: 3e0443d34a97ba1aa04ee39a412e63f32b749737c252d7805c6cdccd58259528
Reported by kdf-statsdb-8762.