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.
2f364a3d847834b155006388a425b30fbc2f604eae3b6e1268f2184d2998e45f
Both payments are on their chains and locked to the same secret hash 3bf699f01fa4771b660583bc7a56e810d705b3db, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 2f364a3d847834b155006388a425b30fbc2f604eae3b6e1268f2184d2998e45f
- MakerPaymentSpent: cd27a084e07c5a179257429abe610a4952b8592040e0fff33fd7baec1560306c
9a151c9780240d8d3ba3f6c014daf682c51be71c4182ce03f3622e746aca8001
Both payments are on their chains and locked to the same secret hash 3bf699f01fa4771b660583bc7a56e810d705b3db, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: 037ba6d6240d9b5115b906d2aacd105e440be9c5213a91c5e2e087c398639b5a
- TakerPaymentSent · TakerPaymentReceived: 9a151c9780240d8d3ba3f6c014daf682c51be71c4182ce03f3622e746aca8001
- TakerPaymentSpent: c89cce548abca48f3f07bdd884f0872011028bf23c8ed5def394389538429e58
Reported by kdf-statsdb.