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.
1d63823230b0ed419e16f5b4de796fb1e06c072dc6b8aced642188413a4b5809
Both payments are on their chains and locked to the same secret hash 440aa3bc28371f94ae3e82baa26a7317633251bb, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 1d63823230b0ed419e16f5b4de796fb1e06c072dc6b8aced642188413a4b5809
- MakerPaymentSpent: dda2f3a2e39801345ffba42e02fa8a99d23baecdd1eca39f4780c9c426a7251b
b440962b7268f44c456870b143928cca2127a7855c906f9686f39505ece73b5b
Both payments are on their chains and locked to the same secret hash 440aa3bc28371f94ae3e82baa26a7317633251bb, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: 61f6ff66c41a7562933f0c5eca95e02469cce8ccc51d30e569432512e4570563
- TakerPaymentReceived · TakerPaymentSent: b440962b7268f44c456870b143928cca2127a7855c906f9686f39505ece73b5b
- TakerPaymentSpent: de7707d45d4f99eda11b687b52d526a41bb93de160504c1e4e021a9841ecacbd
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.