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.
592a23c57c025a1404abc0b4fe15e71e64f41db4545858eb458ae8222a452544
Both payments are on their chains and locked to the same secret hash 501392b8d84f7aed55f2b2f153bb05ed9f1e1ec0, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 592a23c57c025a1404abc0b4fe15e71e64f41db4545858eb458ae8222a452544
- MakerPaymentSpent: f7d69c9fef28f106ebd28c9bff28d6153422686eb7db8d2cbe90239c2e0f590b
1113b622f608574b67e8154b6f9eb08ff7077d91eb0fb3a62c8532fc6d7ea406
Both payments are on their chains and locked to the same secret hash 501392b8d84f7aed55f2b2f153bb05ed9f1e1ec0, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: e208ea64fe649b687d704a0eaa9c1010181cfa41e3d1b1ab9a191b0714f652e6
- TakerPaymentSent · TakerPaymentReceived: 1113b622f608574b67e8154b6f9eb08ff7077d91eb0fb3a62c8532fc6d7ea406
- TakerPaymentSpent: 46ec24d940dabe063be283b5fb3c866c3c7eea063d7c38e684194e1e4e530c6d
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.