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.
fac64659ab422a4c46d04b4c55987a609b3a6881ee7013c60ba2e530845b7852
Both payments are on their chains and locked to the same secret hash f889ba5515c09eba46ea19d904a78fe2b7a822f5, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · fac64659ab422a4c46d04b4c55987a609b3a6881ee7013c60ba2e530845b7852
6a4533307ce391ac5fddc89095e32f0b05eeeaecbbc61313b19e0fabbf41209a
Both payments are on their chains and locked to the same secret hash f889ba5515c09eba46ea19d904a78fe2b7a822f5, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · 71479eaff07415e570a6a3d6db77faa560a1680e98aeebe1806a494eef094b61
- TakerPaymentReceived · 6a4533307ce391ac5fddc89095e32f0b05eeeaecbbc61313b19e0fabbf41209a
- TakerPaymentSpent · ff2c363193066d6f917fa87a5c17cf1be6debb80011365e7435bda62fa44725d
No anomalies were recorded against this swap.
Reported by kdf-statsdb.