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.
21f0505b9f29a64f8c8cf0b5e8183acec186db320c3f02b368415df8929c48d2
Both payments are on their chains and locked to the same secret hash 2099cc0e0484e85fad3c80cfbb2ac17ef10c16f4, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 21f0505b9f29a64f8c8cf0b5e8183acec186db320c3f02b368415df8929c48d2
- MakerPaymentSpent: 42f7b1d13fe006333d0dedf14f2a1165d7634b91a0247150eab1c0833d4ea7ff
71debfc966c8509b25da3980fe6342a69a1c38f89ca448a018570737f9cf20f8
Both payments are on their chains and locked to the same secret hash 2099cc0e0484e85fad3c80cfbb2ac17ef10c16f4, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 8ef7fab4f2805440e96c81f6ee9ed70ac02812833a3bcd44217594def5dbb674
- TakerPaymentSent · TakerPaymentReceived: 71debfc966c8509b25da3980fe6342a69a1c38f89ca448a018570737f9cf20f8
- TakerPaymentSpent: 64d8d596455e12e446e61a2ee4b53a637631b6178b794b31012143dc3eff9f72
Reported by kdf-statsdb.