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.
bce874563ae77e9d1cf7a9bd9d3d0025c075f382aa3aeca2572e529642476670
Both payments are on their chains and locked to the same secret hash f15e4cccda08bd65aec66d98967001f3917e24ed, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: bce874563ae77e9d1cf7a9bd9d3d0025c075f382aa3aeca2572e529642476670
- MakerPaymentSpent: e399eafb53e5808caec38823acfad7243f15897b4078c35ac55763d9f32ec472
6f04a211966acd922354c2b6bdb3364ba90dd387d1e1481e2585623b6e92fec7
Both payments are on their chains and locked to the same secret hash f15e4cccda08bd65aec66d98967001f3917e24ed, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: e20bac0f380b8086e286a34ffc2e85812b5ffbc4d6c72f1cdbc512e4ec43ae06
- TakerPaymentSent · TakerPaymentReceived: 6f04a211966acd922354c2b6bdb3364ba90dd387d1e1481e2585623b6e92fec7
- TakerPaymentSpent: 50a474aa71a55958ff55df89e95ea0a5deecf708028c23b72149772ab1ff9a1b
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.