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.
5dd19b6cb03e9e50730d47561bfc8260772265b149860ec63de2e9997ed7d6bb
Both payments are on their chains and locked to the same secret hash 63273d22fe35ac885962aad19f4b9cc81e536295, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 5dd19b6cb03e9e50730d47561bfc8260772265b149860ec63de2e9997ed7d6bb
- MakerPaymentSpent: 78bd8236531113a56f07a69696e89defccdc5e8e4ed8af750db4b47761a577a9
e712a1fc9dd79f0b682fefce38c9789de5c82cd7d7d3b6d19a5d98354711de34
Both payments are on their chains and locked to the same secret hash 63273d22fe35ac885962aad19f4b9cc81e536295, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 16c9dfdd455e2efee44640b0c661151214290d054fa01ddcd0f6c770b980e5d9
- TakerPaymentSent · TakerPaymentReceived: e712a1fc9dd79f0b682fefce38c9789de5c82cd7d7d3b6d19a5d98354711de34
- TakerPaymentSpent: 57ae67700b2fdab94d2d21edae4a808cfd92ff2dc94f0ed96b26e5b3637ff4be
Reported by kdf-statsdb.