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.
c7e7cd284d3b03e9e8c9ff4095ebdd29fd7189c31cec6e26c4dd4ae10e6eda5e
Both payments are on their chains and locked to the same secret hash 5106541439b28ca319a182dc6d5bf89d93ecf39b, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: c7e7cd284d3b03e9e8c9ff4095ebdd29fd7189c31cec6e26c4dd4ae10e6eda5e
- MakerPaymentSpent: 7bd726f51bc80a70343f45805b2d61aed7140c599515f2a44118d726f8335674
3914eb37a8a3734251878896e0b7985281bb995a64973e55018cf5718671c00a
Both payments are on their chains and locked to the same secret hash 5106541439b28ca319a182dc6d5bf89d93ecf39b, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: c61eba374f62134564ad52f40efc805bc37cbc9183300c1abfc640f32dfdce82
- TakerPaymentSent · TakerPaymentReceived: 3914eb37a8a3734251878896e0b7985281bb995a64973e55018cf5718671c00a
- TakerPaymentSpent: 09f1d8d35418bea89ddb9e4a2370781d5d47230f8cd68d2511f0e1db4ebf6ad3
Reported by kdf-statsdb.