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.
970f74e50ed3282148e1c6164a4579e84a59caad386d3f46ffd41b1f3c0378d6
Both payments are on their chains and locked to the same secret hash e99c5d191a39288d8b71895fa61946a8ead7d1f8, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 970f74e50ed3282148e1c6164a4579e84a59caad386d3f46ffd41b1f3c0378d6
5105ce93b772594ed06f5fa8fe7ea4dfee3e65bc4fd574a1be0ea47dca5fd844
Both payments are on their chains and locked to the same secret hash e99c5d191a39288d8b71895fa61946a8ead7d1f8, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · cd83fb8bfeec977a8ed98636c0d1478794ced1e0e4d8a4d7636ae9f3a587a3c5
- TakerPaymentReceived · 5105ce93b772594ed06f5fa8fe7ea4dfee3e65bc4fd574a1be0ea47dca5fd844
- TakerPaymentSpent · 1c9c78ca853a2b655b56735c1da184102efad21334b756b8be4b2607baacea2e
Reported by kdf-statsdb.