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.
4f213071b85f68ace93cd11c03a87a64d61df88d70dd379e081df5e85c0ef79d
Both payments are on their chains and locked to the same secret hash 21d7efb355f5ea487b9b17b7f05ede7e726b8fd3, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 4f213071b85f68ace93cd11c03a87a64d61df88d70dd379e081df5e85c0ef79d
- MakerPaymentSpent: d37dc4070e22c30301100ef1d0f859d88cb967dd08083e2069dbfb5f658f4843
3ebddfbf44bdeb5b41bc2a7501799fe040836c46638a1c35157d8db6739d1557
Both payments are on their chains and locked to the same secret hash 21d7efb355f5ea487b9b17b7f05ede7e726b8fd3, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 1d157bb0c6f6e158943983bcffe84a5fa1929544fda6a2a914278ce4ad169d11
- TakerPaymentSent · TakerPaymentReceived: 3ebddfbf44bdeb5b41bc2a7501799fe040836c46638a1c35157d8db6739d1557
- TakerPaymentSpent: 64674d1106358a5295208a78eafac89cc41e940583e2237aab46f5871836701a
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.