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.
57aee3ba1a2ca12eddc18e05b129420205f808baf008d3b204d991955d76eec8
Both payments are on their chains and locked to the same secret hash ad9cb7134517d8abfa41e0f8c3d68f78c5572566, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 57aee3ba1a2ca12eddc18e05b129420205f808baf008d3b204d991955d76eec8
- MakerPaymentSpent: 34240bd7e3e4e9198cb4950e57d0d0f2ba9b74d77876160f024451be31870d38
5b89a7f262ef779badcda9626ddb5e4581ce57747d3edddd5fe59fed04f2741e
Both payments are on their chains and locked to the same secret hash ad9cb7134517d8abfa41e0f8c3d68f78c5572566, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: a1ad2c6369c3594fca2cf77bd636d081853ba6d45286bfca88ac9188db130745
- TakerPaymentSent · TakerPaymentReceived: 5b89a7f262ef779badcda9626ddb5e4581ce57747d3edddd5fe59fed04f2741e
- TakerPaymentSpent: 93b31efe2fcb60789741229bca4b7681fb47307d59ba42f63bada3f47bc87dc8
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.