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.
ff0cc0a08b9e209e618109ed0eaef166945694d95ac984c1f3243b66e4433f84
Both payments are on their chains and locked to the same secret hash 655ee38ee230832ea2463ddcbd8761676fc7836a, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: ff0cc0a08b9e209e618109ed0eaef166945694d95ac984c1f3243b66e4433f84
- MakerPaymentSpent: cc9e5be30c9424362c58bb5d45c4d0c5bb29ee4ec739e6d3016edee83df406b4
eb877fbb8f3cae05b20f4aa46c1ab76681689cfae3a986bd9e53a117128f4599
Both payments are on their chains and locked to the same secret hash 655ee38ee230832ea2463ddcbd8761676fc7836a, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 4bd56134eb5bf7a26ee2faeb1e67bc8166bb9ea710fc97d295cc4d45dc4aa307
- TakerPaymentSent · TakerPaymentReceived: eb877fbb8f3cae05b20f4aa46c1ab76681689cfae3a986bd9e53a117128f4599
- TakerPaymentSpent: ea3f84c73320bdb0d222a57cecb81a066be6952764257791cb400e228e53fa7c
No flags are stored against this swap. Flags are written while a swap sits inside a live pricing window, so on an older swap their absence means it was never assessed rather than that it was assessed and found clean.
Reported by kdf-statsdb-8762.