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.
f6ba694cbf65af5be97268baeaeaf5a38232b2dca948093e5b34a68a769fe8a8
Both payments are on their chains and locked to the same secret hash 49f5b3366a91ab16fe4835d8487ab276d1e2233b, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: f6ba694cbf65af5be97268baeaeaf5a38232b2dca948093e5b34a68a769fe8a8
- MakerPaymentSpent: 3d9157c7ec232d9440b7a8568c2f6e6126166fac5384aefcb11b0e5d96bbc029
19c1194c2b77f576016dc0e037fadb7f69457d9e2afc43f75f1980935c4c8257
Both payments are on their chains and locked to the same secret hash 49f5b3366a91ab16fe4835d8487ab276d1e2233b, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 0a24465a56c656abac850e3f1511a88531fb3f4c260cdc17bb9aa4c20b96202a
- TakerPaymentSent · TakerPaymentReceived: 19c1194c2b77f576016dc0e037fadb7f69457d9e2afc43f75f1980935c4c8257
- TakerPaymentSpent: 02462022346a123e583d4760970eb2fd284a015012efebfc74d1b9b995e63a2d
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.