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.
6a50a7e6a389bf5619c5b54dc6108b701fdba79154e9ad7178ce449431bd43dc
Both payments are on their chains and locked to the same secret hash 7321bb4dfab17ea7b9fa4d70f4f055b0444eed66, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 6a50a7e6a389bf5619c5b54dc6108b701fdba79154e9ad7178ce449431bd43dc
- MakerPaymentSpent: 30a1f11a698df6757da6a38614b89918fc6cffa533821bfbb9c9ffa03e535567
b8acc33885dd888c27aa617efb7222941c21749f1654b0d4d5fbeddc174bf77e
Both payments are on their chains and locked to the same secret hash 7321bb4dfab17ea7b9fa4d70f4f055b0444eed66, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: d4879f73c8a658b788d135a3e24a1753fccf2c34f2e4006d7bfe6c6a6dbd698e
- TakerPaymentSent · TakerPaymentReceived: b8acc33885dd888c27aa617efb7222941c21749f1654b0d4d5fbeddc174bf77e
- TakerPaymentSpent: b453a55c71640fa60c50e4f8a6368b539c03fba2aeb56983c848247f1c876dfd
Reported by kdf-statsdb-8762.