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.
e63c65ed3a2712239d17ae4bb78357e8d848c2ed9f73559649a75dfdead100a0
Both payments are on their chains and locked to the same secret hash 5d4eb213553f82d970ea05038b580835ea2aa127, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: e63c65ed3a2712239d17ae4bb78357e8d848c2ed9f73559649a75dfdead100a0
df877d84f9a04d38151d4b76d3dd6ba0aadcc82a7c83442931db8bcc8c8ed0db
Both payments are on their chains and locked to the same secret hash 5d4eb213553f82d970ea05038b580835ea2aa127, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 81997a551087ced25fe7b377d11ee903ffe3c5911de865eaec643dadfc678d2c
- TakerPaymentReceived: df877d84f9a04d38151d4b76d3dd6ba0aadcc82a7c83442931db8bcc8c8ed0db
- TakerPaymentSpent: 9c9fda4c34c1975b7fcc373bae0f337e99e974467e03c8f6e30be12957342688
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.