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.
afe7599fbd98deebdb396ff8715f5800c547be016da26ebd509f19ba3ac80db7
Both payments are on their chains and locked to the same secret hash f65ac3fe59930613985e59b4b909b64484839685, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: afe7599fbd98deebdb396ff8715f5800c547be016da26ebd509f19ba3ac80db7
- MakerPaymentSpent: f41ec54a25f30adecdbe92d1f1bb80c95208292e2a38208aa8691b11001e446e
cab663f7719a87a1f5626212b4b5946382062673373bb09c6bbcf53b237d79e4
Both payments are on their chains and locked to the same secret hash f65ac3fe59930613985e59b4b909b64484839685, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: c1e34748e54a952bf6aa1e408b795b4c139ab9a4e449257d3e837deccecc26e2
- TakerPaymentSent · TakerPaymentReceived: cab663f7719a87a1f5626212b4b5946382062673373bb09c6bbcf53b237d79e4
- TakerPaymentSpent: 5e837d3f9b29da1108d29ef34302c728765dfe42ff214792e6901e74b89d501d
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.