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.
121681bd9e4e95e910d1b130f2b7ca25b453e785d1a8fdd630be79df5f323bea
Both payments are on their chains and locked to the same secret hash 66fe30a8273fbd4f16370a00d7c87c6bac2425e0, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 121681bd9e4e95e910d1b130f2b7ca25b453e785d1a8fdd630be79df5f323bea
- MakerPaymentSpent: 9f3abe5a600998f1b502e6419cf2a39cc2f3432812d290eb0e402805ca9999dc
6c314ad56f1760d28c4cef62c6669bd2f42eecd2602fa548db6d564eeb601b79
Both payments are on their chains and locked to the same secret hash 66fe30a8273fbd4f16370a00d7c87c6bac2425e0, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 9037d2c32b9af71462aacedcb47f298f8ed68a62a70f1d10bf70a7fde94b4166
- TakerPaymentSent · TakerPaymentReceived: 6c314ad56f1760d28c4cef62c6669bd2f42eecd2602fa548db6d564eeb601b79
- TakerPaymentSpent: 751f47e29fc81f7edc80c641d6370c2d32ace48413ef10fb8b4388a2f2873806
Reported by kdf-statsdb.