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.
7d234944e15f81f7a6bd2233279abdd7ca65ff7f46595a8e46b72695fb6135db
Both payments are on their chains and locked to the same secret hash 192f2ee6a54e08b792dc9c395f04fc9ed01a0a65, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 7d234944e15f81f7a6bd2233279abdd7ca65ff7f46595a8e46b72695fb6135db
- MakerPaymentSpent: 0fa04f6517820461285109bf7332bab159957c31daa5881692358cd4c10013e3
d794ec9e8af17ed55889edfa5b922fe8b4748f84198d458ca787d194a22b9129
Both payments are on their chains and locked to the same secret hash 192f2ee6a54e08b792dc9c395f04fc9ed01a0a65, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 533e3f3836ab7dcdfdac89c7dd4e2eb94d6c545e5fea90ff900db6bf654aef8d
- TakerPaymentSent · TakerPaymentReceived: d794ec9e8af17ed55889edfa5b922fe8b4748f84198d458ca787d194a22b9129
- TakerPaymentSpent: 40280b2cb36b108956222c7cb1063f0210817b2f7c0daa1131c63622e50600b2
Reported by kdf-statsdb.