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.
df4727c36ccb9f6482c472f38001202958a9cdffeb423ead5e66ad2bf56252b0
Both payments are on their chains and locked to the same secret hash d49fb8b543c8e382dc14a4f16fc89f3512faf829, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: df4727c36ccb9f6482c472f38001202958a9cdffeb423ead5e66ad2bf56252b0
- MakerPaymentSpent: f982a7aba0fb73350df45a31a7225817358a50d338ec2cdf977e71bd6a8135b7
f1eaaf08180da4059a51dfbc451b6adbc10cf9ef03ea74ef8a143fb037922644
Both payments are on their chains and locked to the same secret hash d49fb8b543c8e382dc14a4f16fc89f3512faf829, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 9de3043bfa12ca9b571ea1378233deb8c449004256165a079c4342ae82d8764a
- TakerPaymentSent · TakerPaymentReceived: f1eaaf08180da4059a51dfbc451b6adbc10cf9ef03ea74ef8a143fb037922644
- TakerPaymentSpent: dac63998f60308c76473963866d554e46949af17ef09f61b80279982bb6fdec8
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.