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.
e5adc841b08079126cfc607b173f855dca9fbf11c6b229b080de98285a814a3c
Both payments are on their chains and locked to the same secret hash ec892d5052dac861f793804546c9e5b939386d8e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · e5adc841b08079126cfc607b173f855dca9fbf11c6b229b080de98285a814a3c
- MakerPaymentReceived · e5adc841b08079126cfc607b173f855dca9fbf11c6b229b080de98285a814a3c
- MakerPaymentSpent · 929d11e18ebf3cec72e27306c866eb06f2b6715350b387ce95328a2a39c5bfdd
256187970468b1fe90b91a52e2f5d6224ebd7d1c697487e18e9fd8866f5cc9d8
Both payments are on their chains and locked to the same secret hash ec892d5052dac861f793804546c9e5b939386d8e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · ae72d83ffe40cb0fc3fe8467e791e6e844a24555018bfff909cfb3bf83ae0024
- TakerPaymentReceived · 256187970468b1fe90b91a52e2f5d6224ebd7d1c697487e18e9fd8866f5cc9d8
- TakerPaymentSpent · 2b9d84334c2986e1b0adafa18cf4a213ad48ed096e7b88e2139ec5696de56fe1
- TakerFeeSent · ae72d83ffe40cb0fc3fe8467e791e6e844a24555018bfff909cfb3bf83ae0024
- TakerPaymentSent · 256187970468b1fe90b91a52e2f5d6224ebd7d1c697487e18e9fd8866f5cc9d8
No anomalies were recorded against this swap.
Reported by kdf-statsdb-8762.