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.
b243abc2beb2b1d60c447fe8a8735616e54cd7e8504b4c6f2e922688a861f371
Both payments are on their chains and locked to the same secret hash 5553813fb11afd2ec55fffc71142550f1292068f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · b243abc2beb2b1d60c447fe8a8735616e54cd7e8504b4c6f2e922688a861f371
1ab6778c7d9bdd2c2665f22e1e92a69a695954b45b1ef09a676f5d45e5ef6bf8
Both payments are on their chains and locked to the same secret hash 5553813fb11afd2ec55fffc71142550f1292068f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · b3f612f5d9ff16d7e438839a3c0d7aecab9e03c17fe3cae0edfec84a8f3a8766
- TakerPaymentReceived · 1ab6778c7d9bdd2c2665f22e1e92a69a695954b45b1ef09a676f5d45e5ef6bf8
- TakerPaymentSpent · 97083a7d61b66e19761961b57660dfa1d1c206418324a6723ea496a9284373de
No anomalies were recorded against this swap.
Reported by kdf-statsdb-8762.