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.
c7f323dbdb89580dae0c0e2a2c187679a186fd78bd0b74064ff602c759881ea0
Both payments are on their chains and locked to the same secret hash 3a346ddd22e447536aa71d06a54d616f69bf7b42, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · c7f323dbdb89580dae0c0e2a2c187679a186fd78bd0b74064ff602c759881ea0
9b84603a0ff88fb2c4956a58da379a965b944825821462882eccce8edc2edf09
Both payments are on their chains and locked to the same secret hash 3a346ddd22e447536aa71d06a54d616f69bf7b42, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · 457ce01eb155b980b8e02a6cd4e05d40c6145181a8ab6bbf6ef7580223f6284a
- TakerPaymentReceived · 9b84603a0ff88fb2c4956a58da379a965b944825821462882eccce8edc2edf09
- TakerPaymentSpent · 7085c0f35b3622ba37889b4d43a561c35f8bf38a08532b7138dd280621f87307
No anomalies were recorded against this swap.
Reported by kdf-statsdb-8762.