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.
d67826aa6314b6f1571d01a85e7e387eae43c81f47d2599cf018cc0385038510
Both payments are on their chains and locked to the same secret hash 492ce3e399a091278d1d4295f6cbc655455aedda, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: d67826aa6314b6f1571d01a85e7e387eae43c81f47d2599cf018cc0385038510
- MakerPaymentSpent: ecdff1a95f5ae61224fc39b597a0c9a822d335f6e562097e9eb35809bad00cbd
52563c18c5cf8e4fca6ed58965c83f47d31f04f69ced17482c19788b25782a47
Both payments are on their chains and locked to the same secret hash 492ce3e399a091278d1d4295f6cbc655455aedda, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 557564bface14e5a8e71e0dc2d9d0f3695452fdf9bbee8b9866464aa093b5a2f
- TakerPaymentSent · TakerPaymentReceived: 52563c18c5cf8e4fca6ed58965c83f47d31f04f69ced17482c19788b25782a47
- TakerPaymentSpent: 84ba9050ebcd04d47525a110e759cd54aed46f3388ce40d16f816017e83f75e0
Reported by kdf-statsdb.