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.
60e05d32c562229d6c06e662910083e343573f7420f19cb29f7a86e2a4185ed0
Both payments are on their chains and locked to the same secret hash a5a9981dc836136539aa867875092d6f4dff1649, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 60e05d32c562229d6c06e662910083e343573f7420f19cb29f7a86e2a4185ed0
805a6ec2773ee95ae11c3c640698b9fe6ad5b7cc3da0012d6718b3d40b5dc17c
Both payments are on their chains and locked to the same secret hash a5a9981dc836136539aa867875092d6f4dff1649, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · 35c7aa0f17ac6499fed4910cdf07595c510d9b9132e585c2d9c81d5db18dfa23
- TakerPaymentReceived · 805a6ec2773ee95ae11c3c640698b9fe6ad5b7cc3da0012d6718b3d40b5dc17c
- TakerPaymentSpent · 74eddbf0395670741cda35872cf86307913c7b11867d1243949334f7f69cbb1d
No anomalies were recorded against this swap.
Reported by kdf-statsdb-8762.