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.
9bbb3d2cf82dcd5dbde14e4ed65933fdb040fb40557003ca288c1dcb98e3a2b4
Both payments are on their chains and locked to the same secret hash a439861bff1c16c3a4882032072d11f1b5ba5afd, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 9bbb3d2cf82dcd5dbde14e4ed65933fdb040fb40557003ca288c1dcb98e3a2b4
- MakerPaymentSpent: 27bbac4d560d51960824710f83388d4166005531c22004d71fda4842d7a9252e
9f3b3faab2b6c0b2a23d78fd34f61e3e2d5b94248cbe1758dea0edc6f78be3be
Both payments are on their chains and locked to the same secret hash a439861bff1c16c3a4882032072d11f1b5ba5afd, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 231772c554c5cb644fab1c0369f453c1010ca00876718b7898210db0976e59ce
- TakerPaymentSent · TakerPaymentReceived: 9f3b3faab2b6c0b2a23d78fd34f61e3e2d5b94248cbe1758dea0edc6f78be3be
- TakerPaymentSpent: 43e9b81c4c3c34bca6e53ec64f58f31c030ebe42a7e4d9b7757093f5849c2d2d
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.