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.
064069bfa7581c05fce69337462917a10783a5cf2c942f31ef2ed5e34ca7fe42
Both payments are on their chains and locked to the same secret hash bbd6674bfc68eb43e829d7e58513d844d63c09b1, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 064069bfa7581c05fce69337462917a10783a5cf2c942f31ef2ed5e34ca7fe42
bae8692a70222225704dc0ba1081bb3bda209fe3def9a8d272eefbde77b528a2
Both payments are on their chains and locked to the same secret hash bbd6674bfc68eb43e829d7e58513d844d63c09b1, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 48296dbc9a9d597f2b1a454a60f805e527a6e741854a9580ac1eb316dcb99130
- TakerPaymentReceived: bae8692a70222225704dc0ba1081bb3bda209fe3def9a8d272eefbde77b528a2
- TakerPaymentSpent: d644a1811c2a1545ee838fc67fd6421344be7e02bbeaf613ee3d384dc26aa402
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.