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.
2775bf41a0240aae49daf1992e2349322972028b8f0f573d6c8570c342dce89f
Both payments are on their chains and locked to the same secret hash 6fb35b4247825be82dbc382a642dbcac808f7467, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 2775bf41a0240aae49daf1992e2349322972028b8f0f573d6c8570c342dce89f
- MakerPaymentSpent: 298515fa61f171591af6d315c36b287dedd4c1d49d54fe7300f5a289df98add2
f67f7708a68af72cd809aa30dd689d40940f83e635aac932f5502847fa12bff3
Both payments are on their chains and locked to the same secret hash 6fb35b4247825be82dbc382a642dbcac808f7467, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: afc2d85d9d347d064a96aef58b4a434098854ed6acd67ea18ce0f8b39f686e17
- TakerPaymentSent · TakerPaymentReceived: f67f7708a68af72cd809aa30dd689d40940f83e635aac932f5502847fa12bff3
- TakerPaymentSpent: 23e6befa325268adb0fa41b48bf1bc8863c834568a044526082dc8e73e3c677e
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.