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.
9295c9b5da26b550f173a0143766c0a9cceae97d4ed00eaf45f089a5bfe296d0
Both payments are on their chains and locked to the same secret hash 47a1ccb8b6cdd5ce3274501290f6627612ced434, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 9295c9b5da26b550f173a0143766c0a9cceae97d4ed00eaf45f089a5bfe296d0
- MakerPaymentSpent: 2dd11e62fe487c3d4643b10b91143ab797a7672de791e4f43f34c3cb2dcf7432
432c845b6ac57f925c7327fcddae2aa91383ad198801e3d03f7827042242fe09
Both payments are on their chains and locked to the same secret hash 47a1ccb8b6cdd5ce3274501290f6627612ced434, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 8d2fcafe30c046a334e437fe61b81ad54a74d053a02ed0d5807ada8eff765702
- TakerPaymentSent · TakerPaymentReceived: 432c845b6ac57f925c7327fcddae2aa91383ad198801e3d03f7827042242fe09
- TakerPaymentSpent: 1d6b98788e323030c4ddb21d37ff220d02f308da076fa307af167d91e2c0f7e0
Reported by kdf-statsdb-8762.