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.
55daa2a45b63fd30dbc37210ae722aff9e6d263e2274c2412389129d02f50e2e
Both payments are on their chains and locked to the same secret hash 50b4eab1cd4f8f0edddb3fe071108549fe4b2f6d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 55daa2a45b63fd30dbc37210ae722aff9e6d263e2274c2412389129d02f50e2e
- MakerPaymentSpent: 66dec3a702c07d3157e10230b82c8d907554026ccc33227d6bcdee8fb831ff68
439af18304104fe30580e25246167983ad78f16e8ad2930f460d24e6010bc25a
Both payments are on their chains and locked to the same secret hash 50b4eab1cd4f8f0edddb3fe071108549fe4b2f6d, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: ed09cee346b6586c9a37db7e45eefc2e9f88aa00696ddbb4d879196126a4a52a
- TakerPaymentSent · TakerPaymentReceived: 439af18304104fe30580e25246167983ad78f16e8ad2930f460d24e6010bc25a
- TakerPaymentSpent: cea0ff64779e5a78b673e114cdebf23022e0d987cb91fce988d1bd86e5bc7c9d
Reported by kdf-statsdb.