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.
735760f7cf1c58d0b60d496dfcce042087c1eb225e20fc19e6ee5f6309e74ac3
Both payments are on their chains and locked to the same secret hash 22ba24af5575f3e539bcdd19136516de63a051ae, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 735760f7cf1c58d0b60d496dfcce042087c1eb225e20fc19e6ee5f6309e74ac3
- MakerPaymentSpent: e03f195ae729da4dea79975cd5be6819803e8f8b5ea428e13080f74f54d7c5fb
0918ade5c73743c4f77c75b0b305e372560cc0d9ab72e3c397a155b9be891088
Both payments are on their chains and locked to the same secret hash 22ba24af5575f3e539bcdd19136516de63a051ae, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 569a640d89b3ce93b89f03c61eab16d93b5025fbf2ca39c609f8609b3438d9dc
- TakerPaymentSent · TakerPaymentReceived: 0918ade5c73743c4f77c75b0b305e372560cc0d9ab72e3c397a155b9be891088
- TakerPaymentSpent: 172ef45fe8daff0bbe82f36ce90982600a37a4963afc7296ab8e6974b381e023
Reported by kdf-statsdb-8762.