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.
bfc7ce18ab3838a9f9500ce283eac81fc214746dac3dbd9edc43ead45d3f56eb
Both payments are on their chains and locked to the same secret hash c42ca2df6468f141cb93c32bd1ddbfedec9fe698, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: bfc7ce18ab3838a9f9500ce283eac81fc214746dac3dbd9edc43ead45d3f56eb
a0944ca923a80bf12a61add23d16372bc376f11b78480d44353d2c469b32c0bd
Both payments are on their chains and locked to the same secret hash c42ca2df6468f141cb93c32bd1ddbfedec9fe698, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 200a2caae086322d54d5ad15dd26c3ddb9664dc952b725ec33a2a8c936ca42c7
- TakerPaymentReceived: a0944ca923a80bf12a61add23d16372bc376f11b78480d44353d2c469b32c0bd
- TakerPaymentSpent: 65a13ac3df63f10ccec3951216d8a5e7c333bd9ecd846f25b559372a68ce7cb6
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.