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.
b4b376a39d36af6e50e8c5961c847484fd421e6bf1ee669d6ed8ed82d04d9198
Both payments are on their chains and locked to the same secret hash 619d7d7d1be818d18eed285ec0762a5a5bf3eeab, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: b4b376a39d36af6e50e8c5961c847484fd421e6bf1ee669d6ed8ed82d04d9198
- MakerPaymentSpent: 2cb564fc78be4d9591dee5eb6ed9859bba9a90d1c97a49faa47040278213242e
597488c5b51e59d77b259dc4393c432f4d40767ad77efaa1c1aebca02653a302
Both payments are on their chains and locked to the same secret hash 619d7d7d1be818d18eed285ec0762a5a5bf3eeab, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 3da20e6c026c21e40d1df3f7c2ab315467ef6533f7ab6b2b210bc52beab0a718
- TakerPaymentSent · TakerPaymentReceived: 597488c5b51e59d77b259dc4393c432f4d40767ad77efaa1c1aebca02653a302
- TakerPaymentSpent: 30aeccd98053c5dd07307021b16856d5a29c145a083939c4348e4e7fafffa6ac
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.