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.
5f2d69cc65d1d36cca878fd4878c1f0910d7e7c30cca86e57cc1fbfc32f23062
Both payments are on their chains and locked to the same secret hash 13a1843aa37c862dc6d3dd1bc12cef3ef32cfc81, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 5f2d69cc65d1d36cca878fd4878c1f0910d7e7c30cca86e57cc1fbfc32f23062
- MakerPaymentSpent: a82c6ff9fbc26745d2043c9e3613a5e13b870c282d8729680a16e71c76315368
1543aa85d169921145f33bda971e1eaff24b834053d62ed55c11047944f4b900
Both payments are on their chains and locked to the same secret hash 13a1843aa37c862dc6d3dd1bc12cef3ef32cfc81, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 74cb156c8777864ab27ae087cedf5ee29b03c52fc8dd84782797a5b091eaddad
- TakerPaymentSent · TakerPaymentReceived: 1543aa85d169921145f33bda971e1eaff24b834053d62ed55c11047944f4b900
- TakerPaymentSpent: 91e9049bd37e676bf9b7ef77aaeb7a89ff38b3b3dbaaddd26f39e8a50f2f74e4
Reported by kdf-statsdb.