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.
f691c35f8181690b91962910aa8c4d220f7c9c5711f55bf37d53297dd7af45f6
Both payments are on their chains and locked to the same secret hash 605aacf62126bfc02f7c0a383e1bc450bf2b130b, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: f691c35f8181690b91962910aa8c4d220f7c9c5711f55bf37d53297dd7af45f6
- MakerPaymentSpent: 794347caa754aac369fd640b2ccdbca4eba3e750b01ba06b594cec45b51e3d82
4e706ad11274b5a094b48550fcf5f9327bdfc47a699eb1561499272a026bb932
Both payments are on their chains and locked to the same secret hash 605aacf62126bfc02f7c0a383e1bc450bf2b130b, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 3fc47135f8ffc0b310daccf18ef5b74c55b35245e07edc7e86712899533bf5fb
- TakerPaymentSent · TakerPaymentReceived: 4e706ad11274b5a094b48550fcf5f9327bdfc47a699eb1561499272a026bb932
- TakerPaymentSpent: a833128a106544f79a7497202bd2a61bf85394b8f34e60f28b6e1ebf4c71eeff
Reported by kdf-statsdb-8762.