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.
1a90112a2a7279c6c5f0b3a57d5f9ae7d09267f4154af0bb8148d4ae3fb95e40
Both payments are on their chains and locked to the same secret hash ba475ef46f189e9c5ccea8f51ea19668304435af, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 1a90112a2a7279c6c5f0b3a57d5f9ae7d09267f4154af0bb8148d4ae3fb95e40
8d5f141d5d95c4602e01a708456569e6677bc2a1b6fd3325be9856fc48df1e9b
Both payments are on their chains and locked to the same secret hash ba475ef46f189e9c5ccea8f51ea19668304435af, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · f55130915224321adddec5a70a9b4c89142e948c8caec951769b87f865732d54
- TakerPaymentReceived · 8d5f141d5d95c4602e01a708456569e6677bc2a1b6fd3325be9856fc48df1e9b
- TakerPaymentSpent · 731bb34809824dcca34118a4ac0ff5ba0789fa37d31c0c382d32c940eea186ce
No anomalies were recorded against this swap.
Reported by kdf-statsdb.