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.
cfc008010838eab86c8798b4010b5e7ce05ed51892787e1225d150d236db8c57
Both payments are on their chains and locked to the same secret hash 0d81f9b1e83eecb05a4da3a32660615418e3b53f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: cfc008010838eab86c8798b4010b5e7ce05ed51892787e1225d150d236db8c57
- MakerPaymentSpent: 891f08d45a0735c8a8ec13e90195b182020e4fb1a6a0a19899bd5e96ee24d848
47c696bc3dff49705404878262f923bfb61c4b0399c312ef612a87cd29b503eb
Both payments are on their chains and locked to the same secret hash 0d81f9b1e83eecb05a4da3a32660615418e3b53f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 8dffed888f520df97050256600e495b92554d99e74752a130e32347420fcd478
- TakerPaymentSent · TakerPaymentReceived: 47c696bc3dff49705404878262f923bfb61c4b0399c312ef612a87cd29b503eb
- TakerPaymentSpent: faadbfdecd5ff9f4406b5df7411ef2f57d9b4386a792aa8b5a5068f2bb1f0fb3
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.