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.
0e69b86073696abb2ee6d2af4f3da829e7a5f6ae4effc6e43e4af11b92e5cdb3
Both payments are on their chains and locked to the same secret hash 29bbc6fa84f29f549926f8e6de4b41ac687ed936, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 0e69b86073696abb2ee6d2af4f3da829e7a5f6ae4effc6e43e4af11b92e5cdb3
- MakerPaymentSpent: fa9ac45391cc5635f81692c4b759ef0ef89b816be6848cacdb5f8efc969ad7b7
5088ef206da07e536bde4ffcd98f80ed25730bc56b0945e8f4cca1c89621dd61
Both payments are on their chains and locked to the same secret hash 29bbc6fa84f29f549926f8e6de4b41ac687ed936, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: a1d641c689795f169a8ef080ea7772bd9b4f04c807fafa6566e8c3f336a8141b
- TakerPaymentSent · TakerPaymentReceived: 5088ef206da07e536bde4ffcd98f80ed25730bc56b0945e8f4cca1c89621dd61
- TakerPaymentSpent: 3a5f52a36742586f70c0b0e7071129f996e9de56c97e19f7970fa150869bbbf9
Reported by kdf-statsdb-8762.