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.
9628b7730d0fadc49d493acec728e1abcdff16afdde982512fc8bfb6d54b2b43
Both payments are on their chains and locked to the same secret hash fc58165e401f38ed2016896c9d32cd9c378f4516, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 9628b7730d0fadc49d493acec728e1abcdff16afdde982512fc8bfb6d54b2b43
- MakerPaymentSpent: 14508a12fd520875b62b2ddd3991d4075b01560bb235dea9ed507e826299f73d
9b6ebcc83eb6f622f51912ba5bd74477041e338b198f2c75d87f09fe2758c602
Both payments are on their chains and locked to the same secret hash fc58165e401f38ed2016896c9d32cd9c378f4516, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: a2cfeae404d506d54792121f9b263753961565f298433eea98e213598ddf0e0d
- TakerPaymentReceived · TakerPaymentSent: 9b6ebcc83eb6f622f51912ba5bd74477041e338b198f2c75d87f09fe2758c602
- TakerPaymentSpent: a074e25955e9efc20309c8911a938457833554633527cf871960a7ba7beebeb6
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.