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.
6b2aa9f0c258e8d0d65a7e72dc5abaf8d3e026e3d981baa65ee9ba3a626c8a44
Both payments are on their chains and locked to the same secret hash 92fd92cd1c7eb641719b53bdb4fecf3e84e66d48, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 6b2aa9f0c258e8d0d65a7e72dc5abaf8d3e026e3d981baa65ee9ba3a626c8a44
- MakerPaymentSpent: 24216f703a334fbd452baac670b7fdada538b793aea75814d0d049b83c7ceb44
39062c42d2514f85f63935c4892df1798a3d3f36d6bfa53dad22534ae56da681
Both payments are on their chains and locked to the same secret hash 92fd92cd1c7eb641719b53bdb4fecf3e84e66d48, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 5b43ebdb6bc6ff534f8dd45ccc2278670c2d7ca0e2823e198e735faccad20100
- TakerPaymentSent · TakerPaymentReceived: 39062c42d2514f85f63935c4892df1798a3d3f36d6bfa53dad22534ae56da681
- TakerPaymentSpent: 9b3b71e1aad69902aba87d009e1d63f09b5ab5fdcc6daee169c48315aae4ddd2
Reported by kdf-statsdb.