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.
68f8d387ddbd3eccf64c8c41f1915eb61edb2cafcc1fe3e7d2db69ad28c983e5
Both payments are on their chains and locked to the same secret hash b77157b0afcef3ec0bfa8904edc1c43bd8aed8f2, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 68f8d387ddbd3eccf64c8c41f1915eb61edb2cafcc1fe3e7d2db69ad28c983e5
- MakerPaymentSpent: 5a4302b1e2d8494e3c1c601735a7e9d22ef51b62fcc210deac2ab396c5a1fa71
53186721dd40c7bd0e402cb22d942af3fbf65445d66b7bf7e6c1d44f1838e0e2
Both payments are on their chains and locked to the same secret hash b77157b0afcef3ec0bfa8904edc1c43bd8aed8f2, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 5480531bae41a443b7d9267e50ba1258d787501c4283a5a521c3129a28a33fcd
- TakerPaymentSent · TakerPaymentReceived: 53186721dd40c7bd0e402cb22d942af3fbf65445d66b7bf7e6c1d44f1838e0e2
- TakerPaymentSpent: a4edce2d02aab97bf10923b04dc800230f777d94959691bc18324532364106a1
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.