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.
8c7e3df4451185007afff61ddab8a4819e3d7dc5571ba90f0de918b8bb2609cf
Both payments are on their chains and locked to the same secret hash 58871e3c2ea3bdf8dac76bae3e67272955910bf4, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 8c7e3df4451185007afff61ddab8a4819e3d7dc5571ba90f0de918b8bb2609cf
- MakerPaymentSpent: b23014ed9867619971d5c848800050bbccf09f147833f7ee104eb6e7da164276
4632158973f99663c3807cd805bbd8c488c200f5a07da0166918cf44e60b37d7
Both payments are on their chains and locked to the same secret hash 58871e3c2ea3bdf8dac76bae3e67272955910bf4, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: e88025da9898d6a1ea518c95aa17a5ebaae1aee8930811ac7ef681a085737627
- TakerPaymentSent · TakerPaymentReceived: 4632158973f99663c3807cd805bbd8c488c200f5a07da0166918cf44e60b37d7
- TakerPaymentSpent: 8079efd57cb8b61023390ceb4416483c8e34be690e4c5d1e5748dae449ded8f4
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.