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.
74e50b6f3e7320aae73f9878e6ddaaa1766a21b2af6761f2d5b5c884ab800dd6
Both payments are on their chains and locked to the same secret hash f1be7dc7d2f1e59170124e4806968980e511a730, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 74e50b6f3e7320aae73f9878e6ddaaa1766a21b2af6761f2d5b5c884ab800dd6
bb4caeee972957dc45733a6280ccdf264b2f78646997a06ae3a10efc92e32c63
Both payments are on their chains and locked to the same secret hash f1be7dc7d2f1e59170124e4806968980e511a730, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · d7c8360df1d21c4f089aaac4c0adf05753bab02f873dcb6b04b00881c82daa88
- TakerPaymentReceived · bb4caeee972957dc45733a6280ccdf264b2f78646997a06ae3a10efc92e32c63
- TakerPaymentSpent · 467ebbdd1ac5aefa6f25dcef87667759ac9a8e051ed8038dfa8062d738a05919
Reported by kdf-statsdb.