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.
7890091b567425aed215fdc2777e7b70419923e9322d25f2fd0f71329bc844f0
Both payments are on their chains and locked to the same secret hash 53edd9cf12bd8be5a9d8412dfc11998941e1193e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 7890091b567425aed215fdc2777e7b70419923e9322d25f2fd0f71329bc844f0
- MakerPaymentSpent: 3be45cfe7029a6d9784904055faf07c7d77dd76cd6e5639bad4e3a9d8c8f1d70
f446603aff816910a3db454bd7f3290f49a03a559466d4d30d029a782829e118
Both payments are on their chains and locked to the same secret hash 53edd9cf12bd8be5a9d8412dfc11998941e1193e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 7773fbc8c5963f72f34e63ab5975accd9fcde7ceb0ee7c0166763e0a1cce10a3
- TakerPaymentSent · TakerPaymentReceived: f446603aff816910a3db454bd7f3290f49a03a559466d4d30d029a782829e118
- TakerPaymentSpent: 56ce227e6b28c281cc8a2a8cc87ae15e1940d8e80cee2fe9be6c2480f1730f4f
Reported by kdf-statsdb.