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.
cb86116d61972bc3cf68f1157a008723e75a9bbd7e28ad03178d7aa2d3b7e531
Both payments are on their chains and locked to the same secret hash a4a49fc624d02a8ec5e5aaf0b39825bb5d395199, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: cb86116d61972bc3cf68f1157a008723e75a9bbd7e28ad03178d7aa2d3b7e531
- MakerPaymentSpent: 27571445937d356ac78003eec982cf188a1eebf919c5e15ef14bff0a7ad1ca0f
7c37900d08c8af6ae6a6d471c0faad77b6497c357146a914b7d8e845f5e1a4e7
Both payments are on their chains and locked to the same secret hash a4a49fc624d02a8ec5e5aaf0b39825bb5d395199, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 251786511d04d1c438535ac2bcde372a733e8aa45386e2201bc2c9b47c154cd9
- TakerPaymentSent · TakerPaymentReceived: 7c37900d08c8af6ae6a6d471c0faad77b6497c357146a914b7d8e845f5e1a4e7
- TakerPaymentSpent: fd4a5a3c9be38f6943203bba8473c58d24ac947e0c1d6ee138adc76abe7bde44
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.