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.
8a8751eff4fe8c28dc9df6fb80277ae9acc203f9f39c61973aaa23290d4bbf26
Both payments are on their chains and locked to the same secret hash 9bd66b10bcf0595be030a726645ca46612d85eba, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 8a8751eff4fe8c28dc9df6fb80277ae9acc203f9f39c61973aaa23290d4bbf26
- MakerPaymentSpent: ea42a522e2a7cff4f6b01b4d3a344990dad55bbd1171103492de41746f83dcf6
5679b035077f424831c17cfef902f457d2c58b0cd251c7e40668298468dff9ae
Both payments are on their chains and locked to the same secret hash 9bd66b10bcf0595be030a726645ca46612d85eba, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: ce2b63517448e776d0e28df3ede5edf4e84d90068b20c9cad765aad492961dfa
- TakerPaymentSent · TakerPaymentReceived: 5679b035077f424831c17cfef902f457d2c58b0cd251c7e40668298468dff9ae
- TakerPaymentSpent: df504378a47071692e614b4a2641e6a0b230e1893a59f7326ae1ac3a6e480905
Reported by kdf-statsdb.