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.
7a7df010fbc9a670c7bd4d3ab1152d85bd9616caead7f51bcdbdf5d1c164979a
Both payments are on their chains and locked to the same secret hash 252942c96f9f61e764b93b012dd81a0199cd3c07, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 7a7df010fbc9a670c7bd4d3ab1152d85bd9616caead7f51bcdbdf5d1c164979a
63f56e48c753dd2928a3909ab8afec4b71468d1c1c931034fd4eb6a66becea6a
Both payments are on their chains and locked to the same secret hash 252942c96f9f61e764b93b012dd81a0199cd3c07, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · 65fe4dad6d7af5fd5f1f3ac35fbd0f6580dc5739c7f55cc2b7f4d5a232fc73cf
- TakerPaymentReceived · 63f56e48c753dd2928a3909ab8afec4b71468d1c1c931034fd4eb6a66becea6a
- TakerPaymentSpent · 734ea4dbd1e75751d473de2ba5522962d78ba259f18693db830278df483904a4
No anomalies were recorded against this swap.
Reported by kdf-statsdb-8762.