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.
474a2bb19a0b8e7944f4f273e8f5bf276bb51b2d705588cfefe17de7cfc81235
Both payments are on their chains and locked to the same secret hash 1899ae89c4b5f63bb4ea2d7371cd8f0ac9e69d61, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 474a2bb19a0b8e7944f4f273e8f5bf276bb51b2d705588cfefe17de7cfc81235
a1bb8e625ad3cddf3f0cc7a96d6fb4e4419a05501911d93cd002bbc73ae9f8b0
Both payments are on their chains and locked to the same secret hash 1899ae89c4b5f63bb4ea2d7371cd8f0ac9e69d61, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · 03fa46b31a0c191baa4d1d32eb8f773cfc6fae923171486b69c226ec312dece6
- TakerPaymentReceived · a1bb8e625ad3cddf3f0cc7a96d6fb4e4419a05501911d93cd002bbc73ae9f8b0
- TakerPaymentSpent · 2574d263511a0e0ec22165b0d86b141fb3e97e71241e3a43cfa8c9faaae47673
No anomalies were recorded against this swap.
Reported by kdf-statsdb.