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.
d6646d1621a6b6f102fcd0335c23c0568110f07f399ce159282a284af132bf5c
Both payments are on their chains and locked to the same secret hash 9adfdc9d365e174d5b236601c1da8219daca6da0, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: d6646d1621a6b6f102fcd0335c23c0568110f07f399ce159282a284af132bf5c
- MakerPaymentSpent: 1a23889a24ef7cd34ab55a1551c0b9fd8f78b413071ca93e9f2ee5b1b170edb2
fb2899af6fbae266870798c9f3b7a31db9e36f8df4b4d989eec430388e8e1d4b
Both payments are on their chains and locked to the same secret hash 9adfdc9d365e174d5b236601c1da8219daca6da0, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 4342abc51c39b4aed9314231c3d2147f7a27163aaaef4f04123054501525f1e4
- TakerPaymentReceived · TakerPaymentSent: fb2899af6fbae266870798c9f3b7a31db9e36f8df4b4d989eec430388e8e1d4b
- TakerPaymentSpent: cbe9c697612874df4559f06721a6d3fb540fb7dc84ec1bd512f0fab25bab1cb8
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.