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.
a7b746626896dc1ecdb8029473b8df84db874e2a7b5a6195e80148262e560de7
Both payments are on their chains and locked to the same secret hash 0c5e32ecdc81ac347b72108e7318e9170978140e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: a7b746626896dc1ecdb8029473b8df84db874e2a7b5a6195e80148262e560de7
- MakerPaymentSpent: 66d0eed56f631b54822ea3db6ed944d03dde3988f71833f7e4bbd747fe35cf2e
c1e559f967ca4d896b63035abdacf11a4a211425a964abc29360784392463a80
Both payments are on their chains and locked to the same secret hash 0c5e32ecdc81ac347b72108e7318e9170978140e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 9ca8cb38c65e7f00a6e5ec1a529e88b39e54d778e3ae0712e089a37f46a28126
- TakerPaymentSent · TakerPaymentReceived: c1e559f967ca4d896b63035abdacf11a4a211425a964abc29360784392463a80
- TakerPaymentSpent: 2036773790c67bdd1a106ea3e4679822b7c6e8b619fdfabc09c9741e76a89344
Reported by kdf-statsdb.