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.
01ad0ede4f6e281baef0c79acbd96cd4db574c97cfbf537d505a55051628dee6
Both payments are on their chains and locked to the same secret hash 162773df217c3059b180bd45c273d61bfb1f8295, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 01ad0ede4f6e281baef0c79acbd96cd4db574c97cfbf537d505a55051628dee6
- MakerPaymentReceived · 01ad0ede4f6e281baef0c79acbd96cd4db574c97cfbf537d505a55051628dee6
- MakerPaymentSpent · e533598931ecaf269cd195a5eb6760e07a0d5a02d588a5d273c5baab4f6fb753
e265dd0befeb487cf7c67de43a2587ab781d865e950bebfaa230cf0a1c5e07e2
Both payments are on their chains and locked to the same secret hash 162773df217c3059b180bd45c273d61bfb1f8295, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · 4cb46ff820eff5c81b54f0ec7df6401a5dc5fa3a2afe0cad19b47487dfe1d4d0
- TakerPaymentReceived · e265dd0befeb487cf7c67de43a2587ab781d865e950bebfaa230cf0a1c5e07e2
- TakerPaymentSpent · 5826c2ea09542f3a8e2772d5418bc2a05f17ebe9937cc55070243c6a005de4d6
- TakerFeeSent · 4cb46ff820eff5c81b54f0ec7df6401a5dc5fa3a2afe0cad19b47487dfe1d4d0
- TakerPaymentSent · e265dd0befeb487cf7c67de43a2587ab781d865e950bebfaa230cf0a1c5e07e2
No anomalies were recorded against this swap.
Reported by kdf-statsdb-8762.