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.
429e1d5451ea35dddb028f0ce0ee76906df3d12ba5e1bd3b3372d9a015f78acd
Both payments are on their chains and locked to the same secret hash a0681dfb299c8b6f2c67d8bd4217974dfc2d83a1, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 429e1d5451ea35dddb028f0ce0ee76906df3d12ba5e1bd3b3372d9a015f78acd
3f74f32e1e408d3267a1efc4d3c1da9201448b29fa4307daf4ea36aea68604ab
Both payments are on their chains and locked to the same secret hash a0681dfb299c8b6f2c67d8bd4217974dfc2d83a1, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · 90dbfb4bb31292e183e614f88da389b707f81eeb2a9e4d66df5796810ea22b84
- TakerPaymentReceived · 3f74f32e1e408d3267a1efc4d3c1da9201448b29fa4307daf4ea36aea68604ab
- TakerPaymentSpent · 5a6aa472bbe29486ac9d2417f04e130b9bec3bffbe10fde27dbf6a9ab2a01fe3
Reported by kdf-statsdb.