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.
dd55346b57294c269225fdbd01e04413d53ab4bc5294472e496df9e0421e071a
Both payments are on their chains and locked to the same secret hash dd8271c08498c715651cb5e047dd408f139ad39c, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: dd55346b57294c269225fdbd01e04413d53ab4bc5294472e496df9e0421e071a
- MakerPaymentSpent: 0a34e8197087dde100b12eb5040e26c32bfecd69ad6a619ae1ae65ddc497505e
6bf751422da8e7c98940866ea3eaee62052413a062b1740097903b9b683a585b
Both payments are on their chains and locked to the same secret hash dd8271c08498c715651cb5e047dd408f139ad39c, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: d3e938b251c3be7d8d488c74a9b3d3fd5abbf9b61cb338c9ddbdfc47be7d8a72
- TakerPaymentSent · TakerPaymentReceived: 6bf751422da8e7c98940866ea3eaee62052413a062b1740097903b9b683a585b
- TakerPaymentSpent: 9fa6dbc9ebd329cfd2308fff04de43eba8c21de217cb3ab593a4ec1b8820eca1
Reported by kdf-statsdb.