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.
4dcad31922c055aa3ee560f9d3ba3f4802ce336f7e4ec1e57f5b9b6b375a14d1
Both payments are on their chains and locked to the same secret hash efab1a00f6b2403ac2c91880badc08e3cd7a391f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 4dcad31922c055aa3ee560f9d3ba3f4802ce336f7e4ec1e57f5b9b6b375a14d1
dea8db03b859b8975fb383e1e14d11aec59a95de97adc02721b2b739a2601fe0
Both payments are on their chains and locked to the same secret hash efab1a00f6b2403ac2c91880badc08e3cd7a391f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · 3fc61b8fb022c3a6cfe40618d63c4a3fbfb80cd9d298f97c975b543219dffeca
- TakerPaymentReceived · dea8db03b859b8975fb383e1e14d11aec59a95de97adc02721b2b739a2601fe0
- TakerPaymentSpent · 33d4936187e8cd367be934a36d898bf1a1cfa382c0638af30666dd48fc16cc39
No anomalies were recorded against this swap.
Reported by kdf-statsdb-8762.