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.
0df9a1b1bf113b4a39f193fb203a1269e5eecd1269a658d9dec55ea90be809ff
Both payments are on their chains and locked to the same secret hash 162574c83ff57f6a571b31eb3ee4a96ec8e28652, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 0df9a1b1bf113b4a39f193fb203a1269e5eecd1269a658d9dec55ea90be809ff
- MakerPaymentSpent: d75efb3663a3e74f829bbee0d04f2555054ba205027388c088e8aa172709fe59
92634217f6df028db485c4ee0bb79594411245ef5af448592fa5390a57d74f84
Both payments are on their chains and locked to the same secret hash 162574c83ff57f6a571b31eb3ee4a96ec8e28652, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: b1601a7afd8f19bdba495dc0345072a97a0755f5560beaf5e88b2d98c1217b2b
- TakerPaymentSent · TakerPaymentReceived: 92634217f6df028db485c4ee0bb79594411245ef5af448592fa5390a57d74f84
- TakerPaymentSpent: ca794cc994406da792d95f098863135b50f0215eb29d1bc4d4757d6ec92932d9
Reported by kdf-statsdb.