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.
08fe3a04d099aa43918c740ec02bfe3d0c12fc3f541e0bd46080cbad4a571336
Both payments are on their chains and locked to the same secret hash ed13ba62f2df6530b818ec3e4ba05da3b765128d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 08fe3a04d099aa43918c740ec02bfe3d0c12fc3f541e0bd46080cbad4a571336
- MakerPaymentSpent: 6a7616d615962900b4110c197743434f3556b71af3f003b4bdcc7e5a9bae1e1e
247a870476908cd2fd84727a985a242b057e87dbfce3812924341b490ed6837a
Both payments are on their chains and locked to the same secret hash ed13ba62f2df6530b818ec3e4ba05da3b765128d, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 23a57b3d55afaeb70fdfefaebab1141cd62e27097cfe5ccbc12600be5e40a98c
- TakerPaymentSent · TakerPaymentReceived: 247a870476908cd2fd84727a985a242b057e87dbfce3812924341b490ed6837a
- TakerPaymentSpent: 66a9c42f92970940b44c6a86755a652c3c2844b4f6458873ff5b356ed9417d76
Reported by kdf-statsdb-8762.