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.
ebe1f48e85bd3049f396b908625aae5e40efdd4b4713718a7d5c7e16e2561d59
Both payments are on their chains and locked to the same secret hash 397d1f6022153a3398e8210e33eb33f7a11879c4, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: ebe1f48e85bd3049f396b908625aae5e40efdd4b4713718a7d5c7e16e2561d59
- MakerPaymentSpent: 5cfd1fb5b243ae08079aa5e8760401588076f550fe6b79e103f1dc8677c96e9e
1c2f8f4a7c7a31f18786836228cef3efeaff94a449af6dd0a2315eaec8e12b94
Both payments are on their chains and locked to the same secret hash 397d1f6022153a3398e8210e33eb33f7a11879c4, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: e0e3d73184883ea2b18803ecc7a4ce6bf7a417cc867ca2b6751e3136ed2c1499
- TakerPaymentSent · TakerPaymentReceived: 1c2f8f4a7c7a31f18786836228cef3efeaff94a449af6dd0a2315eaec8e12b94
- TakerPaymentSpent: 06f41341de1be988dbbefcc42d0699436e3cbc251a7f9e9c98981f10720fb4ee
Reported by kdf-statsdb.