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.
76cee97543b1ce1708b3106291e7f639c9ff18253fc0255229f4058ffd14a504
Both payments are on their chains and locked to the same secret hash 83073a4bb591a466979a08bfc141c70e043af802, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 76cee97543b1ce1708b3106291e7f639c9ff18253fc0255229f4058ffd14a504
d786d9b552daf8028ab3cf149c6f27b79d147fdaf94726ccc7ea7e75c71cbb11
Both payments are on their chains and locked to the same secret hash 83073a4bb591a466979a08bfc141c70e043af802, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · 1c745c6d37de96a5ed16e7e5fc6ba5a7b452a23a96a4d54011113a7e78d20488
- TakerPaymentReceived · d786d9b552daf8028ab3cf149c6f27b79d147fdaf94726ccc7ea7e75c71cbb11
- TakerPaymentSpent · e2d6a2a03d0a6fef4664fc5301acd8defb7545e0d190a78cca939cf96846d322
No anomalies were recorded against this swap.
Reported by kdf-statsdb-8762.