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.
b7cff0cf3230c905dab8010f6ddc6637def79c5e05ac6b4f66a527518e1c6f98
Both payments are on their chains and locked to the same secret hash 4099749f14b73eec4ca5fd8433959db43d121a70, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: b7cff0cf3230c905dab8010f6ddc6637def79c5e05ac6b4f66a527518e1c6f98
- MakerPaymentSpent: ff9989ca00fd76670414ef0c344e01944175989f9b7f9b5db27f537433f5f07c
76784ccafc9584d5d84297ee0dacbb91043c327cc956c1e87789988871481e7b
Both payments are on their chains and locked to the same secret hash 4099749f14b73eec4ca5fd8433959db43d121a70, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 7ba88d47ab874db67235deed1bb1e5abbc56d0dec6854e063edee0d51763e716
- TakerPaymentSent · TakerPaymentReceived: 76784ccafc9584d5d84297ee0dacbb91043c327cc956c1e87789988871481e7b
- TakerPaymentSpent: e3adda5d4d3dbf469ab9eefcb1fc714bd62d7d4df3f966efe0271727417c826c
Reported by kdf-statsdb.