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.
0b3f78d2c3eaf81cb93022bc435db8a3749f52eeebeb1e3d1471a73ad8a7b1b2
Both payments are on their chains and locked to the same secret hash 9d035ccb15e7ba96590bbf756170c0e4e4857341, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 0b3f78d2c3eaf81cb93022bc435db8a3749f52eeebeb1e3d1471a73ad8a7b1b2
- MakerPaymentSpent: 3739db6208ce64c89131fd9a23ff0e4bfb002dff85f2ba672450c88373fdb172
eb4ef2c6d6b9f41c64f2e3a551f8200d1b3f027ed42c9757a97fff7863ba95c6
Both payments are on their chains and locked to the same secret hash 9d035ccb15e7ba96590bbf756170c0e4e4857341, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: eccc7e345b07eb4668a7810b109da151b9378da80c6e96602e8e0ac54edea4c4
- TakerPaymentSent · TakerPaymentReceived: eb4ef2c6d6b9f41c64f2e3a551f8200d1b3f027ed42c9757a97fff7863ba95c6
- TakerPaymentSpent: 1f38461ac6dbf7dcea994b4e9e2fd11f9d77771b1a733242c3b4e53b9daac835
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.