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.
558e2671ce2cf411a87e9c8f9bb1da0da4ff7340bafdae05f0aded222978b6a1
Both payments are on their chains and locked to the same secret hash b7fbac614ad1c8f1ad7b72e0733aac4e070550e5, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 558e2671ce2cf411a87e9c8f9bb1da0da4ff7340bafdae05f0aded222978b6a1
dea0a66f622c23663082e4c4fb321e4cef5c4abeaa73a82a6b0a659a7d6b4045
Both payments are on their chains and locked to the same secret hash b7fbac614ad1c8f1ad7b72e0733aac4e070550e5, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · 729be551ae519ddafbaf4ca611f2461baafe3e946b6d6ca607ea7bc5b4a277a4
- TakerPaymentReceived · dea0a66f622c23663082e4c4fb321e4cef5c4abeaa73a82a6b0a659a7d6b4045
- TakerPaymentSpent · 28705d4b65220e225f6e2d60275cdaa4046ccc200afc83c04779ac07ae334c9e
No anomalies were recorded against this swap.
Reported by kdf-statsdb-8762.