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.
8a68467ab5342f4ee0fe048b93955c2d76e1411a6eedda8e46df4ff70a91cf32
Both payments are on their chains and locked to the same secret hash 842bf9206f16590f34c9c8e6539811bcb3d23223, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 8a68467ab5342f4ee0fe048b93955c2d76e1411a6eedda8e46df4ff70a91cf32
- MakerPaymentSpent: 5925931d4a987279e171202621a7db72e87c02feac9d65ccc4fc5f65119868e9
d608216b821cc5f2faa736fd6c47b304c85cdad68cae9171b3a56ed2127916d2
Both payments are on their chains and locked to the same secret hash 842bf9206f16590f34c9c8e6539811bcb3d23223, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: acf423f992198b7f67eb73928ecf58b8eed90232acb80953f86592f0d3d12c44
- TakerPaymentSent · TakerPaymentReceived: d608216b821cc5f2faa736fd6c47b304c85cdad68cae9171b3a56ed2127916d2
- TakerPaymentSpent: 986ab9772824246a24b4a3a3df5fb99b157ada72af92b612a13cf6a6168514b7
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.