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.
596942d97b2d8b4af5d0c33408eb4ad3b4f2ea42dd2fddae4699419f3a72d0b8
Both payments are on their chains and locked to the same secret hash bf332f68195c2679d94209faad3ddbde5f67b3a5, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 596942d97b2d8b4af5d0c33408eb4ad3b4f2ea42dd2fddae4699419f3a72d0b8
- MakerPaymentSpent: e64bc88a53b13b9a4453a7727f92d07c4c69662b9ec134e29afd9b4a43817068
f32142684f4af499c3bdb56005e17894c0c3249071fbb7969f664e247a5c7f98
Both payments are on their chains and locked to the same secret hash bf332f68195c2679d94209faad3ddbde5f67b3a5, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 4659b671b2ea174889ea053cb9756f9b2cf2e9a487ef2401f16f6db479875f91
- TakerPaymentSent · TakerPaymentReceived: f32142684f4af499c3bdb56005e17894c0c3249071fbb7969f664e247a5c7f98
- TakerPaymentSpent: b36a7cb951d5883f1398e0412b3783765c0bbe1ddbdb4431968a3a49d13870d8
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.