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.
927f14044cf4d4312917918e501106808d7ec18ec2f654e2d362f3084180a07d
Both payments are on their chains and locked to the same secret hash d982fd72ba2cd66ce33b980d2794a0a7755ae1a6, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 927f14044cf4d4312917918e501106808d7ec18ec2f654e2d362f3084180a07d
- MakerPaymentSpent: f67e327c4674befa35d1a54bb44db421eca187fd170d35f94bfa46cb1013dbf6
db76613f05bf3a17bcd780d6b402d06c35156b0653855021480aa86047ab2b6e
Both payments are on their chains and locked to the same secret hash d982fd72ba2cd66ce33b980d2794a0a7755ae1a6, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 4b20ae6c99d8c1ab0181978b0ec1483cb90150baad5111dc69652fe2a2e774d0
- TakerPaymentSent · TakerPaymentReceived: db76613f05bf3a17bcd780d6b402d06c35156b0653855021480aa86047ab2b6e
- TakerPaymentSpent: ff0314f237d0685da89bd3f7f6699fbc650e93cfbda24c0834210d250b37d2ad
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.