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.
577df6ffec3fd1f37f646ad994463163b633d5df8cb457a69cf6dad5ee3f35a2
Both payments are on their chains and locked to the same secret hash 7a2a6880a1cd62a3aa0cbab3ad7a7e2819a8de4f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 577df6ffec3fd1f37f646ad994463163b633d5df8cb457a69cf6dad5ee3f35a2
451bd29fa463d7a5469ae8008c99530a17277cb2a3e53d565e108a76b963e0b9
Both payments are on their chains and locked to the same secret hash 7a2a6880a1cd62a3aa0cbab3ad7a7e2819a8de4f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 1583f0c67b354bfb48b0c3cc0670b1788099123e7a4e3a906c0f3e95d9c00408
- TakerPaymentReceived: 451bd29fa463d7a5469ae8008c99530a17277cb2a3e53d565e108a76b963e0b9
- TakerPaymentSpent: 3b4d672ff2fc2d32e52d6bdc8374dd6b72f74642c28f0a24c8ff68955db12707
Reported by kdf-statsdb.