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.
3750e919c97b98c1f4cf563fe8736db7ad6f03659d89ec4aaa5f75a07868f05e
Both payments are on their chains and locked to the same secret hash ccaf41fef8a688fbbee381f71d55be6b7d120273, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 3750e919c97b98c1f4cf563fe8736db7ad6f03659d89ec4aaa5f75a07868f05e
- MakerPaymentSpent: 8345387e964c1a248abfb7d504a01057425f16f268f8c4a43aaac48cc1200013
a9dc5d573f177c01e5a5dc46675a18474bffbb9442a1e863070854a8a6019dc1
Both payments are on their chains and locked to the same secret hash ccaf41fef8a688fbbee381f71d55be6b7d120273, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 5fa752ce274536b7f91ffbaf57658a5cfc5634a79a271bb994e3727d68790533
- TakerPaymentSent · TakerPaymentReceived: a9dc5d573f177c01e5a5dc46675a18474bffbb9442a1e863070854a8a6019dc1
- TakerPaymentSpent: 144016445863622fe4e1f58633803d0109745646a44bc8983ddb8a9c769b8d78
Reported by kdf-statsdb.