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.
86d046a70e2147b2a0ac5c3eb7a42f61d59e297de46c372df5f5dc06be717c70
Both payments are on their chains and locked to the same secret hash c7625eb27eb2a7892b17dec3e0f03152edc9689e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 86d046a70e2147b2a0ac5c3eb7a42f61d59e297de46c372df5f5dc06be717c70
- MakerPaymentSpent: 4f3963108f7cc4b41bccebb2b6cecf309c62b29cc359b2bf19d5bd9cb589ff0a
209c6d5baa7fa1d8369ae97edda813e5ad85d984ff095ab9a9a251f1d3a704eb
Both payments are on their chains and locked to the same secret hash c7625eb27eb2a7892b17dec3e0f03152edc9689e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 3ba4d1698cdeb957430f20c57c1c41f7e1eaa234079ba6e72cf0874f38f8a9da
- TakerPaymentSent · TakerPaymentReceived: 209c6d5baa7fa1d8369ae97edda813e5ad85d984ff095ab9a9a251f1d3a704eb
- TakerPaymentSpent: 203b14805ba9cfca9a6dc014159f00a9d38ca882c61be2310d5f70e3484451a6
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.