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.
85aa0f785191ed006bf54cc5f549e3fd8b1e5cf4e92eaeb68735edd3dc2e4406
Both payments are on their chains and locked to the same secret hash cb3bc44d87e668591967b5feb24089c7bf262504, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 85aa0f785191ed006bf54cc5f549e3fd8b1e5cf4e92eaeb68735edd3dc2e4406
- MakerPaymentSpent: 7f7e70ed6b145217d707b29add6e748f18d4187fe2df885a9e58699f14cd9591
6e0bb090176671c96b50bcb47e37473822b465b6a8f110f3c7630088d40f4742
Both payments are on their chains and locked to the same secret hash cb3bc44d87e668591967b5feb24089c7bf262504, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: 7a6e937c617ba41b153a6144c15196312839a5775330239a313f9cad832d20b9
- TakerPaymentSent · TakerPaymentReceived: 6e0bb090176671c96b50bcb47e37473822b465b6a8f110f3c7630088d40f4742
- TakerPaymentSpent: 95d654dc6df70adda9e77d81c4227dd857244d958280809a0a054fe33418f712
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.