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.
32beac728e2e2d392c1d509967a0252950094c85be474be0678f61b6dbcc52c5
Both payments are on their chains and locked to the same secret hash d5168d84ec710d1a55d938df2c4961d8821586d5, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 32beac728e2e2d392c1d509967a0252950094c85be474be0678f61b6dbcc52c5
- MakerPaymentReceived · 32beac728e2e2d392c1d509967a0252950094c85be474be0678f61b6dbcc52c5
- MakerPaymentSpent · 557501c4eda9a43ff18559291920deaccac5a0a635d9f5e38f083dadfeee82de
5049472ff3ab0f2853118fafd00f4237f94bdf027e8231453ee6e6dae1043ca3
Both payments are on their chains and locked to the same secret hash d5168d84ec710d1a55d938df2c4961d8821586d5, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · 709c5e391713180d7ee045cb7c6db1700517868162d8e80ac3564f749c320b82
- TakerPaymentReceived · 5049472ff3ab0f2853118fafd00f4237f94bdf027e8231453ee6e6dae1043ca3
- TakerPaymentSpent · f6abaf144bdf43d30df60535dd3df003f0de8056ed550414ea51f6a1a5cb2c17
- TakerFeeSent · 709c5e391713180d7ee045cb7c6db1700517868162d8e80ac3564f749c320b82
- TakerPaymentSent · 5049472ff3ab0f2853118fafd00f4237f94bdf027e8231453ee6e6dae1043ca3
No anomalies were recorded against this swap.
Reported by kdf-statsdb-8762.