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.
c86315a44b417dc0fdb312fb8318f7dc53e825f84cdd00c7ae44594a92d7b750
Both payments are on their chains and locked to the same secret hash 687aa7449e850f7d67ebb5f55f0fd06ece909a09, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · c86315a44b417dc0fdb312fb8318f7dc53e825f84cdd00c7ae44594a92d7b750
84e7cbf416b43cf0441f1de1a7396fe73163b95b6cca60030501329f314114dd
Both payments are on their chains and locked to the same secret hash 687aa7449e850f7d67ebb5f55f0fd06ece909a09, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · 33237ec0d193137700191a63de65dc5f2a8fb65f9a5370b30b2955b89c01a71a
- TakerPaymentReceived · 84e7cbf416b43cf0441f1de1a7396fe73163b95b6cca60030501329f314114dd
- TakerPaymentSpent · 81e6a91cc57b98a04c148ba9c98d9454103bafb4b8942f038886f841d01992d7
Reported by kdf-statsdb.