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.
26a4804ebeeaf839a93ab418ef490a874b3aa04d9608ca82bcc73b0ea7e14761
Both payments are on their chains and locked to the same secret hash 804af5be77569ae7e0782feb4de0d8ac6f9ec093, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 26a4804ebeeaf839a93ab418ef490a874b3aa04d9608ca82bcc73b0ea7e14761
b9fd529639ba868a467454ac1f09d950554489115f38251d35a83fee3beb41ef
Both payments are on their chains and locked to the same secret hash 804af5be77569ae7e0782feb4de0d8ac6f9ec093, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 2a94a9f62b863c8cff4b42a5d55039e2942334173bc4c626b69f0c0cf9559324
- TakerPaymentReceived: b9fd529639ba868a467454ac1f09d950554489115f38251d35a83fee3beb41ef
- TakerPaymentSpent: 78789b8f1768f64c37ceadf2bd4b665fa39cd90579d129b7c4f044d07d20b7f0
Reported by kdf-statsdb.