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.
b6acf769729d1d08f24ddc98b8bdf23e6b57ad089b160cbdc4ae540a94f10fc1
Both payments are on their chains and locked to the same secret hash f5f723d44b3cadd0ead42804685695a6fd31086b, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: b6acf769729d1d08f24ddc98b8bdf23e6b57ad089b160cbdc4ae540a94f10fc1
- MakerPaymentSpent: c168202f1407faff1acacc0ae0813adbd88e6fb299ff7e52f4ca5c32eebeb0b0
d4ca7915dcfb78868b98cb26beb48ea1a4a8c79f75ca29c91862345f31eae1d6
Both payments are on their chains and locked to the same secret hash f5f723d44b3cadd0ead42804685695a6fd31086b, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 05db247f7e674ff58be432a4f50f7da124077b9e926bed6e4cffa580f14c2173
- TakerPaymentSent · TakerPaymentReceived: d4ca7915dcfb78868b98cb26beb48ea1a4a8c79f75ca29c91862345f31eae1d6
- TakerPaymentSpent: ae779cae2a6a87e74fd20bddbd546de1ee97a60a4658be3adf995f3b3ae716ae
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.