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.
0f84eec3da31650ee99e3203ed3340eeb91460848a664e29de4ef983e50c4b8b
Both payments are on their chains and locked to the same secret hash 05d4ebf780edddca6d3559abbf6fc1f135cd6d72, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 0f84eec3da31650ee99e3203ed3340eeb91460848a664e29de4ef983e50c4b8b
- MakerPaymentSpent: 192ebcf21cffbfd5204b6042d9aa554a2ebd7b3feba171cefe0de24c0446d5e8
a4572a749e480f44abfda6208948db0050affd17f2045c401e20eb4211b16308
Both payments are on their chains and locked to the same secret hash 05d4ebf780edddca6d3559abbf6fc1f135cd6d72, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 1f8c1534f6541cad97d4dbbedbe70f246beafb1a7e660b951510651a08f991cc
- TakerPaymentSent · TakerPaymentReceived: a4572a749e480f44abfda6208948db0050affd17f2045c401e20eb4211b16308
- TakerPaymentSpent: 2e41f160c1c9acdfee29b8e4b1da2ebf626e62ddb03c49d79e152a9c89d8b5d2
Reported by kdf-statsdb-8762.