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.
9e66a98fb22ea47063df71ceefd91abc39398f19dd5ec8896aacdacc75281912
Both payments are on their chains and locked to the same secret hash e527bf6d66aef1137844699990ae5e02984a711f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 9e66a98fb22ea47063df71ceefd91abc39398f19dd5ec8896aacdacc75281912
54d13949411de46dd0eb20dba69240160ec0d934c10ce286f09f8fed98be163e
Both payments are on their chains and locked to the same secret hash e527bf6d66aef1137844699990ae5e02984a711f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 046d4af6115587b15d9b1fa85ffc308a53c43aa1c1c0e0d3dceee6766a228aa8
- TakerPaymentReceived: 54d13949411de46dd0eb20dba69240160ec0d934c10ce286f09f8fed98be163e
- TakerPaymentSpent: 810fbccaeaba1c57d659660b42c411df4310efd7c755935ebebb381723f739ba
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.