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.
10e55cd93b2f6d1fb78bfd4c1ea3a57ddbc553839af4835a81e598d2c2e1017a
Both payments are on their chains and locked to the same secret hash a43060715c6c77dd09f61d145e1e851f22a77268, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 10e55cd93b2f6d1fb78bfd4c1ea3a57ddbc553839af4835a81e598d2c2e1017a
- MakerPaymentSpent: 44b27ded94f1205d073f5d4eb896631d399edc513ed59b1772a9d1de2a1f657c
8ed44d49e629c97e63ee7f5686a395ac354ed721f0322f46f6a8a13ec7c681cc
Both payments are on their chains and locked to the same secret hash a43060715c6c77dd09f61d145e1e851f22a77268, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: c2d1963887ec54a87df77decc0da8ae628d942a2422a771ee2ae3baea29516f3
- TakerPaymentSent · TakerPaymentReceived: 8ed44d49e629c97e63ee7f5686a395ac354ed721f0322f46f6a8a13ec7c681cc
- TakerPaymentSpent: 906dbcf2c362ad47b99f296053465a23b2f2fa9bdd5e878d00cdd495db31c817
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.