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.
bf2f32c6216a941c2775490cf0fa0259dd46fdb8f461ad0194709078d7644944
Both payments are on their chains and locked to the same secret hash f9c82915f1757d2f345cc9751fdbf028464359b1, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · bf2f32c6216a941c2775490cf0fa0259dd46fdb8f461ad0194709078d7644944
bd1c2a7269dabd10c4789d8846686fb553f20e8bd2e87b3e0221c9d2f083d9bb
Both payments are on their chains and locked to the same secret hash f9c82915f1757d2f345cc9751fdbf028464359b1, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · 76120e539ba6a43ed57d8f490f27b75d5308208952f6e3c8e08ad85db28da80d
- TakerPaymentReceived · bd1c2a7269dabd10c4789d8846686fb553f20e8bd2e87b3e0221c9d2f083d9bb
- TakerPaymentSpent · 786ef9a99caa62a9012bde027223ae971dd275631c686e7e89b3381a48eb5ae7
No anomalies were recorded against this swap.
Reported by kdf-statsdb-8762.